yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] swaney:
hell naw.. do u kno wat its called.. or do u jus want to pm the link.. either way is cool
[General Questions and Answers] stevevaius:
Hi All, I have a project on my mind to start after I have finally time. I would like to add android device to my E46 330i car to increase its safety features which has not even a parking sensor. I would like to add reverse&front camera with recording features, OBD diagnostics on display and google maps, google voice assistant. How should I start? I have a so-so programming skills (Pyton, R, JS...) but not good on hardware other than installing PCs. Really need your guidance. Best regs
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Change log

2021-10-12 - FINAL build

Security String 2021-10-01

Bromite System Webview and Browser updated to 93.0.4577.83

2021-09-10

ASB Security string 2021-09-05

microG 0.2.22.212658-2

2021-08-07

ASB Security string 2021-08-05

Bromite System Webview and Browser updated to 92.0.4515.134

F-Droid updated to 1.13

Fix in WiFi randomization

2021-07-10

ASB Security string 2021-07-05

Bromite System Webview and Browser updated to 91.0.4472.146

microG 0.2.21.212158-2

Kernel: Many sec. patches applied (taken from Divest-OS)

AuroraStore 4.0.7

2021-06-13

ASB Security string 2021-06-05

Bromite System Webview and Browser updated to 91.0.4472.102

microG 0.2.19211515-9

Kernel WLAN driver (qcacld-3.0) patched to include mitigations against "Frag" vuln.

2021-05-10

ASB Security string 2021-05-05

Bromite System Webview and Browser updated to 90.0.4430.204

Upstreamed microG (no new version)

Update: AuroraServices 1.1.1

2021-04-10

ASB Security string 2021-04-01

Bromite System Webview and Browser updated to 90.0.4430.59

F-Droid updated to 1.12

Update: AuroraStore 4.0.4 with AuroraServices 1.1.0

2021-03-08

Security string 2021-03-05

Kernel slightly patched

Bromite System Webview updated to 88.0.4324.207

Bromite Browser updated to 88.0.4324.207

F-Droid 1.11

microG 0.2.18.204714

2021-02-05

Security string 2021-02-05

Kernel slightly patched

Bromite System webview updated to 88.0.4324.141

Bromite Browser updated to 88.0.4324.141

F-Droid 1.10-alpha-234

microG 0.2.17.204714-5

2021-01-22 - Initial build

Security string 2020-01-05

Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)

Pre-installed AuroraStore

Bromite as default browser (87.0.4280.106)

eSpeak TTS engine (FOSS TTS solution)

Additional security hardening features listed below:

Cloudflare as default DNS (instead of Google)

Privacy-preferred default settings

Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)

Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)

Firewall UI (under Trust)

Increased max. password length of 64

No submission of IMSI/phone number to Google when GPS is in use

Default hosts file with many blocked ad/tracking sites

Privacy-enhanced Bromite SystemWebView (87.0.4280.131)

Extra control of sensor access for additionally installed user apps (Special access under app permissions)

Constified JNI method tables and hardened bionic lib
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] todevrandom:
OnePlus7TPro:/proc # zcat config.gz | grep USB_ACM
# CONFIG_USB_ACM is not set

What a shame. Can you set ACM support in kernel config?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
Wow, what a work!! Thank you for this.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Will have a look this week - the kernel right now is identical to the LineageOS "official" kernel (plus some patches). Is my understanding correct, that this is needed for USB tethering?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] steadfasterX:
@MSe1969 wow.. Ok first of all thanks ! It's great seeing another privacy lover put there !

2 questions:

1. Why not going with /e/ ? Or at least push your great extensions (like firewall ui etc etc) upstream there? Just curious if there is anything preventing you going that route

2. Did you ever tried locking the bootloader with the OP 7t pro? I have read that it is possible when saving the signing key via fastboot
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Hi, thanks for the positive feedback.

I know /e/ and I also watch their repositories from time to time to obtain new ideas or simply see, what they do (same I do e.g. with GlassROM, GrapheneOS, divestos, ...). More a question of my personal taste to have my own build variant, which I provide meanwhile for a couple of devices (LineageOS 14.1 f. falcon & peregrine, a 16.0 treble build for Huawei P9 and 17.1 builds f. oneplus3, osprey and hotdog), but definitely no "hard" reason or any negative attitude towards /e/.

Regarding locking BL, well - as I develop for this device, locking the BL does not provide any advantage for me, in the contrary...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] todevrandom:
Yeah, for communicating with Arduino/Discovery board from Linux Deploy. It works in lieage16 for samsung. I had tried to build Lineage18.1 today following official guide but run in some issues while building (maybe openjdk version). Next try will be the next weekend.

Many thank's!

Anyway, thank's for this ROM
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] steadfasterX:
Afaik it is possible to lock the bootloader when using own signing keys (which you do) and just enabling the signature in fastboot. A big advantage and you won't loose anything as you can still put custom ROMs on it as long as they have the enabled signature .. Or what do i miss here?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
I have tried to root it but i'm in infinite loop and power 20 s can't stop it

Edit power + volume up works
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Well, for example fastboot boot testkernel.img wouldn't work any more. As said, "me doing development work" - for a user of my ROM it definitely would be beneficial. To be honest - I am not 100% sure, whether it really works (I would have to gain more information first, the 7T is brand new to me, I know it is possible with the 3T).

Would you mind testing it and confirming? (I know: If it doesn't work - you may end up in having to fully wipe, so not an easy answer - you wanted also to re-assure before simply doing it)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
OK, glad you've found the way to stop the loop.

What exactly have you done (step by step), when you attempted to root the device?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
- Transfer Boot.img from your rom to phone

- Flash boot.img with latest Magisk Manager

- Transfer patched-magisk.img to PC

- Connected phone to PC with cable

- Launch Power shell Windows

- Command > ./adb reboot bootloader

- Command > ./fastboot boot magisk_patched.img

- Bootlop before i can start for flash definitively

BTW great rom, smooth and battery friendly.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
Since i have changed accent color with Styles and Wallpapers in settings, the app crash. I have reboot the phone many times. I have used this option 4 times after a reboot, you will can see it in the logcat

I put a screenshot and a locat file
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] steadfasterX:
Ah ok i see. Well.. Its my DD and so nothing i can do easily. I'll build /e/ for this device as soon as my time permits as the plan was to go with /e/.. Now with the appearance of your ROM I am not sure which to choose lol
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] todevrandom:
Brightness doesn't drop below 33% as seen in Settings while slider at it's minimum position
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I haven't changed any display settings compared to the original LineageOS device config, so I assume the official LineageOS ROM behaves the same.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for the log - will have a look later
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
I have problems with notifications too, if the screen is off, i dont have notifications from SMS and chats (telegram, Signal)

Edit: Notifications fixed, my bad 🙄

Re-Edit: second attempt for root was the good one
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
yes, indeed.

i shortened the steps but that is exactly what I did.

therefore, my supposedly clean recovery is dirty somewhere...

back to cleaning up the whole tree. do you think if I switch_microg. sh defaults then force sync it's enough or should I level out folder, or even rm * - rf?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
@MSe1969

Just a silly matter of OCD, I noticed AuroraStore prebuilt folder is grafted in the root of the prebuilts instead of being in prebuilts/prebuiltsapk ...

and BTW is there a reason you prefer fdroid to auroradroid?

thank you
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
It is important to clean the out folder (e.g. via command 'make clean' or 'rm -rf out' - if you use a different out folder location, act accordingly).

If you followed my documentation and have therefore properly checked out all branches, so the switch script runs w/o warnings/errors, no force-sync is needed. To make sure, you can verify: All forked repositories should show that they are on branch 'lineage-17.1', when calling 'git status' while within them.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
AuroraStore is an own repository, prebuiltapks is a different repository, that's why.

F-Droid simply is shipped as "original" and I don't want to replace it with AuroraDroid for no urgent reasons. Everybody can however download and install AuroraDroid and make use of the shipped AuroraServices to use its install method.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] :
Is it possible to get Play Store working in some way or another, since I'm eager to get Franco Kernel Manager going. But it requires the Play Store. I tried flashing some different Gapps offerings, such as NikGapps and OpenGapps, but none of them seems to be working, because every time I try to install any Gapps related, I get the same error "Not enough sufficient space" or "Not enough space".

It would be awesome if anyone could provide me with help :)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
First of all, the AutoraStore FAQ explain a way, how you can install previously bought paid apps from the play store. Further, you can buy apps on the play store via web browser, even from your PC.

So - as long as this app does not use G*s play store license verification feature (no idea, but honestly, that would be an overkill) - that could be your easiest way forward, worth a try at least.

If you insist on using the genuine play store app:

You can flash the play store app as priv-app over microG, after you purge the Fakestore.apk, and there are some tipps & tricks around in the wild, but that is not guaranteed to work, so you are on your own on that,

I don't really recommend this

, but maybe other forum participants have some experience?

Finally, worst option of all, if you really want to flash Gapps:

This ROM contains some specific hardening measures and is therefore not foreseen to have any Gapps installed. Of course, anybody is free to do, whatever he wants to do with his own device, which also includes to try flashing Gapps over my ROM, despite me not recommending it. But in that case, you're on your own.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
I had some work issues and I cannot dedicate myself to 'practice your teachings', I had some compile errors by some of simply deleting out folder and I had to to a deeper cleaning.

Finally today, after having done a rm-rf * a resync a switch to default and build I completed my compile.

I flashed my signed default recovery to both a/b partitions, crossed my fingers and sideloaded my slightly modified build I previously prepared.....

Success!

Everything loaded smooth and when rebooted it worked as expected (moreso hoped 😅).

thank you again for all the work you've done and help you've given me.

I will surely bother you again (my next target is arranging a remote server, even if I am the only one using my rom and, clearly, it will be simpler to just sideload the updates), in the meantime.

thank you!🎊🎊
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
If you compile the whole rom by yourself, after the repo sync and switch to hardened branch, but before the actual compile, you can replace the fakestore apk for a patched phonesky apk.

get it from nanolx or somewhere trusted.

if you just switch the file and rename the new one as fakestore. apk you can compile with no other modifications.

if, instead, you want to add other apks or other fine tunes, you have to modify /add something more in the base configuration files.

if you read the readme in the microg prebuilts repository you will understand what you have to add/modify.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
@MSe1969

From the previous messages I had not really understood if you are using a signed bootloader. I would like to try relock with my signed build, any clue how I can do it?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
As I develop, I keep my BL unlocked.

Honestly, I don't know, whether you can relock the BL. You could try by using the respective fastboot command. But be aware, that un-locking the BL erases your data, so if you can't boot the OS any longer and need to unlock the BL again, your data is gone. Without TWRP, a backup isn't that easy...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
But having TWRP, even with a locked bootloader it's a bit of a safety weakness,?

Anyways, there is a guy who has made a 99% usable TWRP (no support for OOS10-11 data encryption, no MTP working but the rest seems it's working).

I tried to build it (I want to sign it) but I failed since info are a bit scarce

You might need to pick few patches from gerrit.twrp.me to get some stuff working."

But maybe you can make it work.

here is the github link https://github.com/Systemad/android_device_oneplus_hotdog

I found it in the xda twrp forum..
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Well, to flash a Custom ROM, you need a Custom recovery (OK, with an unlocked bootloader, you could also flash certain partitions, as an alternative), irrespective of TWRP or Lineage recovery (which is based on AOSP) or whatever.

The main characteristic of a Custom recovery is, that it allows you to flash "whatever you want" (within defined boundaries) versus the Stock recovery, which only allows to flash signed stock firmware. So in this regard, if somebody with bad intentions obtains physical access to your device, you are in a slightly worse situation, than with a Stock ROM.

That is why you should encrypt your /data partition.

(The 'famous' Google feature of remote-wiping your device in case of theft however is "feel good security theater", nobody really needs that).

I may have a look, however - I am not really good at "bringing up" a device - and if even the official device maintainers of LineageOS (who very often are also the TWRP device maintainers) didn't succeed so far, I consider this as far from being trivial.

Coming back to your point with the locked BL - as long as you don't use a somehow very restrictive recovery (I.e. an own creation with some extra verification) a locked BL won't really "protect" your device.

To explain it in a very simplified way: A locked BL prevents the execution of the commands "fastboot flash ..." and "fastboot boot ...". The stock recovery only accepts manufacturers signed update-images. Both together, plus mounting the /system and /vendor partitions read-only (and of course no root) protects the device from altering the existing OS other than by official updates.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] bestouff:
This ROM looks like the perfect fit. Is there a 18.1 version planned ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Not in the near future, but eventually, maybe in a couple of months, yes.

To quote myself from a post here some weeks back (scroll back...):

"Frankly, I do not see any "killer" features, which would make me switch as soon as possible.

To me, besides some nitty-critty details (bubbles, prio chats, use location only once), the only effective difference would be to have the ultimate pleasure to see "Android 11" when picking "about phone" in the Settings app."
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
New build with June ASB patches available

Hi all,

a new build is available and will later today also be offered via the Updater app. For manual download and flashing, see here:

https://sourceforge.net/projects/lin17-microg/files/hotdog/lineage-17.1-20210611-UNOFFICIAL-microG-signed-hotdog.zip/download

ASB Security string 2021-06-05

Bromite System Webview and Browser updated to 91.0.4472.102

Upstreamed microG (0.2.19211515-9)

Kernel WLAN driver (qcacld-3.0) patched to include mitigations against "Frag" vuln.

Regards, M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
HI I am trying to build from your source I am getting errors on these repos

error: Unable to fully sync the tree.

error: Checking out local projects failed.

Failing repos:

OTA

art

frameworks/base

frameworks/native

packages/apps/LineageParts

system/core

maybe you still haven't pushed in all on github?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
There is two parts of my answer:

1. Indeed, I did not yet push the patches, I do that always after LineageOS has officially merged, because I want to keep the lineage-17.1 branches in sync. I apply them on my local repos with the repopick command on the lineage-17.1 branch and then cherry-pick to the lin-17.1* branches. (You should do the same)

2. Item #1 however does not explain your issue with repo sync. Did you perform, before synching, a ./switch_microg.sh reference?

What is e.g. the result, when you cd into frameworks/base and execute the command git status ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
I am sure I made a switch reference that went on without apparent issues,

but, to be sure, I repeated it.

Turns up it messed up something and was complaining about some unmerged things in many folders

(if you need it I posted the wall of words here https://pastebin.com/ntRerHvj )

afterwards I have done a git status in frameworks/base and I got this:

rebase in progress; onto 7d8006107f4

You are currently rebasing branch 'lineage-17.1' on '7d8006107f4'.

(fix conflicts and then run "git rebase --continue")

(use "git rebase --skip" to skip this patch)

(use "git rebase --abort" to check out the original branch)

Unmerged paths:

(use "git restore --staged <file>..." to unstage)

(use "git add <file>..." to mark resolution)

both modified: packages/SystemUI/res/values-fr/cm_strings.xml

no changes added to commit (use "git add" and/or "git commit -a")

I think I'll have to hose at least all the folders complaining
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Not sure, what went wrong and needless to discuss. Instead, what you need is a fix.

So go manually into each repo folder, where it complains. There, depending on what git status reports, you enter first git rebase --abort (if it says "rebase in progress") or git merge --abort (if it says "merge in progress").

Next, shoot git status again. Pay attention to the comparison and the remote. If it says for example: "On branch lin-17.1-microG and then later ... Your branch is ... before/behind ... github/lineage-17.1", then you need to first set the remote right: git branch -u github/lin-17.1-microG lin-17.1-microG. (You skip that step, if the remote is correct) Now again shoot git status and look at the status. If it says "your branch is xx commits behind ...", simply enter git pull github <your-branch>. If it says "...diverged ... xx commits ahead and yy commit behind ...", shoot a git reset --hard HEAD~nn, where nn is the bigger number of xx or yy. Afterwards do the 'git pull'. Checkout all other branches and repeat that exercise.

When you are finished, manually! checkout each branch to lineage-17.1 (those in the switch script only), then do ./switch_microG reference and if that runs w/o issues, do another repo sync.

EDIT: Make sure you understand the git commands and do not simply execute them blindly.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
Thank you!

Surely! I always take notes during my adventures, I am learning a lot, mostly thanks to people like you!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Coolmobile2u:
Hi 1+7t pro HD1925 does it fit
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
No!

HD1925 is hotdogg (the 2nd g at the end is no typo, this is indeed a different codename).

This thread is about the hotdog device (HD1910, HD1911, HD1913, HD1917)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] bestouff:
Hi,

I finally took the plunge and flashed this ROM, and now my phone has been on the looping bootanim for half an hour.

I tried an adb logcat but even an lsusb can't find it. Is there a way I can provide some debug info to troubleshoot this ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I would need some more info to be able to help. E.g. exact phone model (see my previous post), and what exactly you did. Did you e.g. really follow the OP instructions 100%, or did you decide to do e.g. things differently?

EDIT: Press vol up, vol down and power simultaneously to force you out of the loop (phone should either power off or land in boot loader, from where you can control next steps)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Coolmobile2u:
都快一个月了，还以为是零件有问题，检查后一切正常
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
English, please!

(see forum rules)

I used "Google translate" to get the following translation:

"It's almost a month, I thought it was a problem with the part, and everything was normal."

My post, which you have quoted, was to answer @bestouff 's described bootloop issue after flashing my ROM.

In my post before, I had answered to you, that this ROM is

not

suitable for your 5G device (HD1925).
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
@[IMG alt="MSe1969"]https://xdaforums.com/data/avatars/s/7929/7929484.jpg?1600604027[/IMG]

MSe1969​

Well, I would like to say, that this is the best supported thread ever. Thank u very much for quality and steaddiness.

The rom is great, reliable and fits all my suggestion of a really good rom. If possible, i would like to donate some bucks.

Great work here , and as i stated before, If u ever switch to 18.1 i'll stay with u for next rom, whenever u plan....

Thank u again, Great job!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
FYI - I have added an FAQ section to the OP.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] bestouff:
I did it exactly as written, without the factory reset.

So now I did a factory reset and it works, excepted I can't seem to give root to Titanium Backup to retrieve my backup and reinstall my apps. Does anyone have a tip to run TB ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
In LineageOS 17.1, the only way to grant root to apps (like e.g. TB) would be Magisk.

If you have already Magisk working: TB does not seem to be actively developed any longer, so not sure, whether your issue may come from that end...?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] bestouff:
Ok I'll try that, thanks