yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Here's a testing build guys https://glassrom.pw/signed-ota_update.zip

Warning: there might be several bugs​

It was personally tested by me and the 3t maintainer. I've lost most of my testers so this hasn't been tested that well

It was only tested on a 3t so far. Users who have op3 should exercise caution before they try this

The changelog:

July 5 2019 security patch

Lineage analytics are disabled by default for new users (for existing users glassrom will preserve the settings so analytics must be manually disabled)

Fixed an issue with devices using 2 SIM cards where either the second or both cards were locked with a sim pin and the system wouldn't let you unlock the second card

Upstreamed sdfat driver

Merged these upstreams: lineage common, android-linux-stable, CAF for msm8953_64, WiFi driver from CAF msm8953_64, sdfat, Google's kernel/common

To be merged: I have no idea what happened to f2fs 5.3-rc1-3.18. It isn't out yet but I'll surely merge it once it's out and release the next testing build

Not merged: there were no changes to the official op3 lineage kernel by the maintainer so nothing was merged

CAF has discontinued support for msm8996's 3.18 kernel branch but for a long time msm8953_64 and msm8996 had exactly the same code so even if msm8996's 3.18 branch is discontinued we can still get CAF fixes from msm8953_64's 3.18 branch
[OnePlus 3 & 3T Cross Device Development] Sytis:
What should a tester do? Just usual usage and searching for visible and severe bugs or get debugging logs and alike? I got a 3t as well to test, if its just simple bug hunting because exams are getting closer and I don't got much time for excessive debugging atm.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Testers just have to use the device as they normally do and report anything that doesn't behave the same way as before but 2 restrictions apply

Testers must not reboot the device at all until the testing period ends

Testers must charge the device overnight to make sure that idle maintenance tasks execute successfully
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Weird breakages were reported in Sweden and Greece with broken mobile data and calls

Updated the build to fix those

Also a few changes seem to have a few rough edges so they were removed from this release. The changelog will be edited to reflect this. They might be added in a future date
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Updated again. Just a few cleanups and nothing huge so you can ignore this update

Remember that the link doesn't change
[OnePlus 3 & 3T Cross Device Development] Sytis:
I could offer testing on a OP3T as well, sadly no OP3 to offer testing with.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay guys I messed up the first testing build

Please follow these instructions:

Upgrade to the third testing build directly and boot it

Go to settings > system > reset options

Choose "reset app preferences"

Confirm the reset. You'll will lose current app permissions and default apps

Once the reset is over if you replaced the system dialer with a third party app you must go to settings>app>default apps and make sure your dialer app is selected as the default dialer app otherwise phone calls will soft-reboot your device

Reboot

Note: do NOT confuse "reset app preferences" with "factory data reset"
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
This third build has been promoted from "testing" to "release candidate"

Approvals: me (anupritaisno1), op3t maintainer (has requested to keep their identity a secret)

I'll wait for a small bit and if no new bug reports come up this third testing build (now a release candidate) will likely be the next release build
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
And it's been promoted to a release build

Here's the glassrom verification entry https://github.com/GlassROM/glassrom-verification/commit/4ac5b6104a21b30b766e0cc63338e236604fc373

Everyone here if you've already flashed the third testing build do not flash the release as it is exactly the same file

For everyone who didn't there is a new release build out

Caution is advised. Remember that the glassrom server can go down. Use enhanced twrp to verify integrity with zip file signature verification before you flash. For build authenticity use the glassrom verification hash

Also a huge thanks to everyone who donated. It really helps
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
New testing build coming out soon. This one will test the features that I removed from the current release as they weren't that stable

There will be no new release until the third week of the next month as there are no security changes or bugfixes that need to be released urgently
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Yes I know I promised a new build but I couldn't really release it

With no response at all from RX the glassrom server is certainly shutting down soon. I'm currently destroying all data on the server

The download server will remain up even after the process however I currently can't build anything new on it and it may go down at any time without notice

A huge thanks to everyone who donated! Glassrom will surely be back in a while
[OnePlus 3 & 3T Cross Device Development] ajash:
VoLte problem
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
We all have some problems in our life....

But hey if volte is giving you problems you can disable volte to make the problem disappear
[OnePlus 3 & 3T Cross Device Development] Sytis:
Looks like the server is completly down now. My mirror is up, but its bandwidth is definitely limited. So don't expect highspeed downloads.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
I have no update from apex technologies yet. I'll let you know what happens in about 2 days

Also what's the link to your mirror?
[OnePlus 3 & 3T Cross Device Development] Sytis:
Lets hope you regain a working server soon.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
I'm looking at a few providers right now. Meanwhile I got a response from APEXTECH that rx group didn't reply at all

APEXTECH have also opened a ticket with aruba (the current provider) to see if they can switch the billing to them so that I can just use the old server again

I might have a few more updates to share tomorrow
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay we are still not up yet but in the meantime I do have something you can use

I signed bromite with glassrom's releasekey https://transfer.sh/CgHAs/br.apk

This is the same bromite as in the f-droid repository for it but has been signed with glassrom keys

There is no need for verification. The app installs on top of a system app with strict signature enforcement. Just make sure it is installing as an update to the webview

Instructions: just install the app as an upgrade to the system webview (android will tell you that you're upgrading a built-in application)

Gapps users: gapps installers might have replaced your webview so this might fail to install

Installing this may break safetynet attestation
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
[MENTION=6493997]Sytis[/MENTION] please upload this to your download server. It might take a while before I get a working server. Sorry about that
[OnePlus 3 & 3T Cross Device Development] Sytis:
Done, but remember my bandwith is limited because I can't get any better connection plan here.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay guys good news. Glassrom will definitely come back. It might take a few days to setup everything however

Bromite webview was updated on f-droid. I don't have a PC or my keys with me to sign the update just yet but it's coming soon

CAF has still not released the august security patches for our device so I can't do much about it right now
[OnePlus 3 & 3T Cross Device Development] Sytis:
Finally some good news :D

Just in time because I planned on updating my server completely which would cause at least one day of downtime. I'll keep the mirror up until your new system is ready though.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay the glassrom server is back

How do I get direct download links from your server though?
[OnePlus 3 & 3T Cross Device Development] Sytis:
You mean directly to the single files instead of the shared folder? Just add /download?path=/&files=FILEYOUWANT to the link I shared. Or what do you mean? :)
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
All glassrom services with the exception of the download server are back

I'm currently recompiling nginx. Since I compile with lto and all the hardening options enabled it takes about 2 hours to compile the webserver instead of just a minute. This might take a while but I must update the webserver version to the latest before I start hosting anything on it
[OnePlus 3 & 3T Cross Device Development] Sytis:
Good to hear, but what the heck are your compiler flags to cause this much compiletime? Maybe my hardware is just too strong but I never took longer than 5 minutes to build nginx or similar with whatever options I threw at it.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
BTW guys don't worry about the lineageos rebase

If you're using glassrom kernels I'll handle the rebased commits and no commit history will be lost

If you're not using a glassrom kernel:

I'll like you to a commit that you can pick after which you can just do an empty merge of the lineage tree to preserve your history
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay guys I asked the lineage maintainer and he refused to answer why the rebase occurred

How to merge for developers: go to https://wiki.codeaurora.org/xwiki/bin/QAEP/release

Then find the CAF tag for msm8996 version 9.0.0 and looks like "UM.7.5" "r1 05300"

Merge that CAF tag into your kernel

Search for qcacld-2.0 and click on the result that links to CAF

Update the qcacld subtree with the same tag

Now git pull the lineageos kernel

Then run this:

In the root of your tree

Commit the current merge with zero changes and you're good

If any developer is affected by the rebase share this message to let them know
[OnePlus 3 & 3T Cross Device Development] Sytis:
Ah, that explains a lot. Thank you for the very detailed insight :good:
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Guys I've uploaded a new bromite build on the server. Please update as needed

Note that this is exactly the same as the official build but it has been signed with my own key to allow installation without root

signed-ota_update.zip

A new beta is out. This fixes certain warnings the build system threw about volte blobs. Volte still doesn't work though. Security patch level has been bumped to 5th august 2019 and f2fs has been updated from 5.2-rc1-3.18 to 5.3-rc1-3.18

Edit: sorry I didn't check correctly. As per google there is no august 5 2019 security patch because no vulnerabilities were discovered https://source.android.com/security/bulletin/2019-08-01.html so the security patch says august 1 and not august 5

Edit: the last edit is wrong. Sorry I was almost asleep when I wrote this

For some reason the merge only committed up to 1st August 2019 in the build repo but security patches up to 5th august 2019 are present in the ROM
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay guys new build is out

Changes:

Updated security patch to 1st august 2019

F2fs upstreamed to 5.3-rc1-3.18

Upstreamed sdfat driver

Google common kernel merged up to https://android.googlesource.com/kernel/common/+/1c575ded9d398bbc931a72dfeb25b97c5dd79759

Bromite users must update their webview manually AFTER installing the update

CAF didn't release a new tag for either msm8996 or msm8953_64

Verifying builds: https://github.com/GlassROM/glassrom-verification/commit/b6544eca3ae1aa00faa6dac8b6cd50a1a6a89581
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Please test this build if you're in India and use jio

https://glassrom.pw/signed-ota_update.zip

Best case:

Volte works fine

Sending SMS over a 4g-only network is not yet supported. Only calling works

Worst case:

It doesn't boot at all

Please be careful with this build. Keep the stable build downloaded as well so that if something does go wrong you can easily switch back
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
I deblobbed the glassrom kernel. It boots and everything seems to work

There is no guarantee that the kernel has actually been deblobbed

The deblob commit where I run the linux-libre script: https://github.com/GlassROM-devices...mmit/f96976166a101365e4182d0b681d007521782f59

Proprietary firmware existed in qcacld-2.0

Also the deblob script patched for an older kernel so there was a build error

I deleted that proprietary firmware and fixed the build error in https://github.com/GlassROM-devices...mmit/222824701ee5ee77f05970db0c174293a00319bd

I then removed the -gnu tag because I'm unsure if it can even qualify as libre: https://github.com/GlassROM-devices...mmit/01dd047f99d5552e628c4b5de5714f2d3691cbc0

Thanks to [MENTION=10096626]Insanely Click[/MENTION] for testing this
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Bromite system webview has been updated again. Please see glassrom-verification for the correct hash

https://glassrom.pw/boot.img is the boot image for testing the almost libre kernel. No guarantees are made. Currently booting with dm-verity is unsupported but it is enabled. You must disable it manually to be able to boot. This is NOT for the faint of heart
[OnePlus 3 & 3T Cross Device Development] :
Good job and nice to see these developments to deblob and make it 'Libre' :good:

Could be one of the reasons to switch from LOS to Glassrom someday....

I have to say that with all trouble from the last months with your server, as the missing website and background info about Glassrom, it just feels less safe and trustfull for me as it did some months ago. I really appreciate developments like yours with improved user awareness, improved securety, hardened kernel etc... but I am not capable of reviewing the code, updates are not that regular as for LOS with a large community and for me it seems more like a one-person job then a real community and so (may be) not a ROM which I can use up to date as long as I can keep my OP3T alive.... :)

Could you share some background about Glassrom, it's community and what we can expect from the OP3(T) builds in the future also (Android 10 and further?)?

A completely different question about recovery.img on your new setup server. Is this the latest twrp build you made, based on 3.3.1.0?

Asking because in your twrp thread link to mirror is not working and do not want to download from 'untrusted' mirrors... ;)
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Information regarding glassrom or more specifically who owns and controls it will never be public

Lineageos uses an automated buildbot to release new builds even if there are no changes. A typical aosp tree only updates once a month so the user only needs an update once a month as no major changes can't be included before the next security patch. Glassrom doesn't use a buildbot and maintainers only build when there are changes

Also read the first post. As long as you use the verification repository you can download from any mirror
[OnePlus 3 & 3T Cross Device Development] :
About continuity; are you the only maintainer for Glassrom at the moment for OP3T?

You did a request for testers some time ago but no idea how large the 'support group' for OP3T is.

Thanks for your answers btw... ;)
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
No I am not the only maintainer. There are 2 others.

There are no guarantees about newer android versions. Security patches will be released but new versions depend on several factors that are determined after the new version is released

Updates will continue until these conditions are satisfied (each is transitively dependent on the requirement before it)

A critical vulnerability is detected in glassrom/android in general and needs fixing

Security patches can be released

Version upgrades can be satisfied

Transitively -> if a version upgrade can be released but a security patch can't be released then the version upgrade won't be released. In other words each item in the list above depends on the items preceding it before it can be satisfied

Security patch -> glassrom takes into consideration both the ROM and kernel at the time of determining the security patch. If either one can't be updated the security patch won't be changed to a newer version
[OnePlus 3 & 3T Cross Device Development] Sytis:
I moved my domain (personal choice affiliated with the old domain), I commented with the new domain on the TWRP thread, it's just not updated in the op. Just verify the files you downloaded from my server the usual way, I don't tamper with them but please make sure for yourself. The server is also just meant to be a temporary mirror. But it should get a fairly high uptime now, as the change is completly done.

I will mirror every file on glassrom.pw plus the two TWRP images. And try to keep them as up to date as possible.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Thanks for the help man. I appreciate it
[OnePlus 3 & 3T Cross Device Development] :
@anupritaisno1, thanks for this long but nice reading.

Would be a good second post for this thread and definitely helpful to get some understanding about the background of Glassrom.

A lot you mentioned sounds very familiar to me. In the past I have used several Linux and BSD distro's for workstation and server usage, always with security as main reason for making my choices. Arch was one of these and also one of my favorite Linux distro's because it was stable, simple, straight forward and easy to setup with some terminal and Linux background.

I have also built Firefox and K-Meleon builds in the past and liked making websites based on pure php code. So a little programming is not strange to me, but after years of computers, I stopped programming myself. It simply took too much time, which I like to spend with family and friends.....

(I think I replaced 'computers and programming' with 'phones and a little tweaking.... :rolleyes:)

I really like the philosophy of Glassrom, thanks again for sharing this background information! :good:
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
New sha3 hashes have been added to glassrom-verification

https://github.com/GlassROM/glassrom-verification/commit/d691cc04edb7f7f1fc75453d8422342f7d43bb12

Sha2 hashes are not going anywhere for now. Sha3 is still relatively new and hardware that can compute sha3 efficiently is rare to come by even today
[OnePlus 3 & 3T Cross Device Development] Sytis:
After trying your libre boot image, dm-verity got triggered and now shows this warning at the beginning. It didn't go away even after flashing the rom zip again. So I disabled dm-verity via Magisk with the libre boot image and the message persists but it boots at least. Also: Doesn't your som ship with los recovery anymore? Because it doesn't get flashed automatically like before. And if we happen to use los recovery, how does one update glassrom because the device isn't detected via adb in recovery mode but it is detected via adb after boot. So the PC shouldn't be the culprit. Other than that, the libre boot image works without issues so far.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
It's technically not fully libre yet as 3 drivers still need firmware loading which don't work at all without and are responsible for core functionality (touchscreen, WiFi, hardware accelerated encryption)

When I released the kernel I already had mentioned that dm-verity didn't work on enforcing mode on it but should work fine from the next release

Recovery not starting adb correctly is a bug I've not been able to fix yet as getting logs without adb already proves to be hard. I'll let you know if I ever find out the cause though
[OnePlus 3 & 3T Cross Device Development] :
Probably stupid question but did not find the answer in previous posts (or did not read well enough...) and do try to understand....

On your server, what is the difference between:

- glassrom-release.zip

- op3_glasrom,zip

- signed-ota_update.zip

And what is the difference between:

- op3_recovery.impg

- recovery.img
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
glassrom-release.zip is for op2

recovery.img is for op2

signed-ota_update.zip can be a testing build for any device. You're not supposed to be doing anything with it

The others are for op3

Read the first post carefully and only use the download links from the first post
[OnePlus 3 & 3T Cross Device Development] :
OK, thanks.

But why not make it logical for everyone by renaming to op2-....., op3-.... and test-..... or even better use separate device directories?
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
I do not think the first post mentions "https://glassrom.pw" and only "https://glassrom.pw" anywhere

All links are in the form "https://glassrom.pw/*" or in other words you weren't really supposed to use the server's autoindex feature. If you are visiting the server and using it's autoindex feature to see the file list then you assume full responsibility for what you're downloading
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay guys a new build is out

Changes: upstream lineage changes

Same kernel changes as the enhanced twrp I released yesterday

Removed audiofx and lineage updater

I also tried to fix volte again. Indian users should definitely report back

No September security patch yet

Due to certain technical issues the deblobbed kernel wasn't updated. It will be updated soon
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
The glassrom kernel now has continuous integration support https://travis-ci.org/GlassROM-devices/android_kernel_oneplus_msm8996

Clang build seems to fail because I didn't implement ARCH_SUPPORTS_INT128 yet. The clang builds are for my reference only
[OnePlus 3 & 3T Cross Device Development] knpk13:
What is the issue with volte?

I just came back to India from the US and I have a US OP3T. I'm using Jio here and VoLTE doesn't work, so I have to use the Jio4GVoice app. Is that because my phone is a US model? Or does stock LOS not support volte? Or some other reason? I'm currently on NLOS and was wondering if I should try Glassrom to see if volte works.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'm aware. But Jio is working. I'm guessing because one out of the 3 used bands is supported and Jio works for data, and calls/SMS through the app.

[MENTION=5842226]anupritaisno1[/MENTION] ah ok, thanks, I'll check it out
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Hey guys there's some issues with the download server right now. We should be back very soon though
[OnePlus 3 & 3T Cross Device Development] knpk13:
I tried the latest build of GlassROM and VoLTE did not work for me. Calls did not work, although it kept saying that there was low signal/no service/emergency calls only, although that wasnt a problem in the exact same area with NLOS (my current ROM). I went out and walked around and still got the same message. I think I should have checked with the jio app to see if it was a network issue or VoLTE, but I restored my backup. I'll probably try it next week or build again when im free.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Glassrom doesn't check firmware and boots regardless of firmware

However using radio does require the latest 9.0.4 firmware. Upgrade your firmware first
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'm on 9.0.5 firmware already, always latest.

And before you ask, no it's not any modded/hacked firmware. It's the original OOS 9.0.5 firmware.