yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] shape_beats:
In fact, I used to suffer from ads from my VPN too, and I didn't know what to do, I even blocked ads with third-party extensions for google chrome, although actually the developers are also understandable why they add ads to their service. I have a friend who knows about this field and he also works with VPNs, and he gave me a solution to this problem, advising me to use a VPN without much obvious delay, and I had a lot of problems.
[OnePlus 9 Pro] TheGhost1951:
Add a DNS such as dns.adguard.com and it will help to block ads. Or this...

personalDNSfilter - Apps on Google Play

A tiny tool to block tracking, malware and other unwanted content

play.google.com
[Android Q&A, Help & Troubleshooting] anx7501:
Samsung removed Cast from the display-settings on a new phone. This makes no sense because Cast has been part of Android core for a while. Anyone know how to re-enable Cast to I can screen-mirror as I did with older devices?
[Samsung Galaxy S22 Ultra] drfundy:
I ditched the s21U in large part because wireless android auto did not work right. After a short time, music would start "skipping". Sounded really choppy and had to use a cable. Works perfectly on my Pixel 6 Pro.

I am wondering if any of you who have bought the s22 ultra and are using WAA can report whether it works well.

Thanks!
[OnePlus 9 Pro] aNGERY:
I don't know if it's just me, but I updated to C.47 by:

Magisk uninstall, restoring stock images.

installing the update

Magisk install to inactive after OTA completes

Reboot.

I have 4 modules. USNF, osm0sis busybox binary, debloater and systemless hosts.

The only way I was able to get them to work was by disabling all modules, rebooting, finding the google play store APK download from APKMirror and installing it.

Now, I have randomly cloned APKs, but they were only ones I debloated. I debloated again and they vanished.

I admit this thread might be a huge waste of your time to read, but if someone is having this trouble, it might bail them out
[OnePlus 9 Pro] dariodamico:
I am in same situation like u with Google play store and Google services play crash .I try everything but no luck .finally idowngrade to os 11. But I'm very intested to know why Google applications crash .The only magisk module installed is : Octavia dialer A12.
[OnePlus 9 Pro] terlynn4:
Wow, good to know this is happening and that you found a workaround. I guess I'll probably wait a few days to install this and see if other people are having issues.
[OnePlus 9 Pro] DavidKalil10:
In c47 version, the 5G option returned in network settings?
[OnePlus 9 Pro] Skenderbeggar:
Not for me
[OnePlus 9 Pro] DavidKalil10:
I've just discovered a workaround isign the app force LTE/5G. With this app is possible to open the Network settings and force the 5G as it was possible in Android 11 using *#*#4636#*#*View attachment 5565863
[OnePlus 9 Pro] Moka UA:
It fails when reaching the middle

View attachment 5566125
[OnePlus 9 Pro] aNGERY:
are you rooted?
[OnePlus 9 Pro] Moka UA:
Yes
[OnePlus 9 Pro] aNGERY:
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot

i'd disable whatever modules you have enabled.
[OnePlus 9 Pro] Moka UA:
Ok..i have root zygisk ..Is there a problem with that?
[OnePlus 9 Pro] terlynn4:
Zygisk is fine, only installed modules should be disabled when you update to avoid possible issues. Most modules won't have any issues, though.
[Samsung Galaxy Tab S8] am2013:
Hi all,

I would like to get some feedback on the AMOLED display quality in regards to uniformity when displaying a grey screen?

Did Samsung improve anything here or do the AMOLEDs still have clouding issues and the displays are not really uniform?

This can be seen using OLED tools with dark green or dark grey.

I have a Tab S3 and Tab S4 both with some clouding visible especially when displaying grey and dark grey.

Got some feedback that the S7 had also some issues. So any improvement with the S8+? Would like to upgrade, but would like to have a flawless display.

Thanx in advance,

am
[Samsung Galaxy Tab S8] blackhawk:
This is all I could find.
[Samsung Galaxy Tab S8] am2013:
Thanks for your feedback. It describes some older panels. Question is if the screen unifromity is better with Tab S8+ or if there are still issues with dark grey/near black as with previous devices.
[Samsung Galaxy Tab S8] Jake.S:
That page is old. It refers about galaxy tab s generation 1 I think, about 8.4 inch and 10.5 inch one, it does not talk about new s8 series.
[HTC Excalibur] rickwyatt:
Sorry Ive Had To Take The Rom Down Because Nrgz28 Ask Me To
[HTC Excalibur] pfunkside:
Hey Rick what do you use Wm5storage for? I've used it to delete myfav 5 from original tmo official rom but I really didn't need it for anything else?
[HTC Excalibur] rickwyatt:
because i have vista and it easyer with it
[HTC Excalibur] outragis:
are any of the bugs fixed on this?
[HTC Excalibur] stylez:
I don't understand why Ricky has to take down this ROM because NRG says so, the right of the ROM is that the copywrite belongs to M$, if you look @ other parts of the XDA forums you will see that more than one person will present a ROM, without being told what to do with what they have cooked, it's an artistic liscence we hold and a right to use it, modern day society cannot prevent the future....
[HTC Excalibur] jdoggraz:
Oh well I guess it was a sign of respect that he took it down... Oh well... I never got a chance to try it which is a bummer...
[HTC Excalibur] showaco:
Sounds like to me you showed respect by having his name in the title.:rolleyes:
[HTC Excalibur] gospeed.racer:
Why not work together for one uber-rom?
[HTC Excalibur] Mikey:
Now Now...

Everything will work out for the best sooner or later :)
[HTC Excalibur] NRGZ28:
I asked him too because today I'm releasing ver 1.1 of my ROM with all the stuff that he added to it, already built in. There's no reason to have two very similar ROMs floating around. I could understand him modifying Kavana's ROM when Kavana was gone, but I'm still here and I can debug my own ROM :)
[Introductions] Iyan Mulyadi:
hi, still use the z00a in 2022, with custom rom ofcourse :v
[Redmi Note 9 Questions & Answers] kenshinta:
Does afwall work in a correctly configured ROM?

Tldr

Browsing through threads here for the redmi nota 8, I caught a mention of someone asking if afwall was working on a certain distro - and for some reason I couldn't trace where it was and if the inquiry was answered.

So long question being: does afwall work correctly, and if so which distro works best with it:

* stock miui itself with a correctly configured magisk installation?

* custom rom (if yes which specific one) with magisk?

I ask as for me the only reason I'd use a rooted non miui rom is to use afwall and titanium backup (and similar backup app) and root specific appops managers.

else I'd stick with stock, use netguard to handle network access and adb only control of apopps

Thanks!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
​

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

GPL compliance:

Kernel source code: LineageOS/android_kernel_xiaomi_sm8250

Working:

Camera (and flashlight)

Mobile Data (4G/5G)

WiFi

Bluetooth

Telephony (VoLTE/VoWifi)

Audio (Record and Playback)

Video Playback

Sensors

GPS

NFC (Except aliothin)

Bugs:

Nothing (?)

Downloads:

Wiki:

Note:

Must follow installation wiki for this device.

GApps can only be flashed on clean installs.

Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

No custom kernels are supported in this thread. Only stock kernel and official builds will be supported.

Flashing LineageOS through custom recovery is not supported and not advised.

For recovery you must flash vendor_boot.img and boot.img

Bug reports:

DO NOT report bugs if you're running a custom kernel, recovery or Xposed or Magisk mods.

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.).

Report bugs here: https://wiki.lineageos.org/how-to/bugreport#reporting-a-bug

Credits & collaborations:

All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

Support:

XDA is preferred for main discussion. But if you need any unofficial support then check this group. We strongly discourage direct contact with any devs through social media.

Credits

:

@SebaUbuntu​

@Sahil_Sonar​

DONATIONS : Paypal
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
SafetyNet

​

By default LineageOS doesn't pass SafetyNet, why?, Check here https://lineageos.org/Safetynet

You can use this unofficial method to pass SafetyNet (Not for rooted users): ih8sn
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] demirlijanp:
I'm on latest miui 13.0.3 do i have to downgrade? Thanks.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
So far only tested with android 11 firmware. You don't need to downgrade if it's working without issues.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Morpheuspt:
Does ok google work?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AkechiShiro:
What lineage features were not implemented ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] demirlijanp:
If someone flash this, please post some screenshots, and some thoughts on how the ROM behaves.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
It should work with gapps.

Expandable volume panel, buttons, statusbar features,etc.. need to be ported from 18.1.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nripat:
Correct me if I'm wrong but Android 12L is a Rom that is specifically created with Android Tablet Devices in mind like enlarged UI. & better multi tasking support to utilize larger screen real estate.

Are their any notable advantage in Android 12L over regular Android 12 from Alioth point of view (Excluding the advantage of on being latest available OS).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AkechiShiro:
Could any contribution be made by someone who just develops a bit if yes, maybe I could help in porting those feature, I don't have any experience in working on Android tho, I can install Android Studio and Gradle for building if that's what used. If there is anywhere where there is a contribution guide, I'll be glad to give my best at it, thanks !
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
You can submit changes to lineageos via gerrit. It will be reviewed by Devs and might get merged.

How to use Gerrit | LineageOS Wiki

wiki.lineageos.org
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jamaladdini:
Could you please share some screenshots of features and specifications if anyone has installed the rom. Lineage Android 12L would be a great rom.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AkechiShiro:
I have tried to build the ROM for Android12 (Lineage OS 19.1) using the code source from Gerrit and the builds fails with an error (at the step 'brunch alioth'), I have asked for help on #lineageos Libera.Chat IRC server and has received those answers "build for Android 11, if you don't know what you're doing", "we know how to solve the issue, it's easy but we won't tell you" and so on. Quite the nice community there btw, feels very welcoming.

So I can't really progress much yet, if you have any resources that could help me get started, feel free to DM me.

I've attached a screenshot of the issue, but since Lineage OS 19.1 is unofficial at the moment, I don't think LineageOS community plans on helping much for now at least. View attachment 5570271
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] LilBlinx:
LineageOS developers are one of the most egoistic and toxic ones. They see everyone as newbie other than themselves. If you build Lineage, you are on your own and don't expect help from them. As I can see, the 19.1 branches aren't updated to reflect latest changes and you are building with 18.1, which you shouldn't.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AkechiShiro:
But where did you see I was building with the 18.1 branch, I see LINEAGE_VERSION=19.1-20220324-UNOFFICIAL-alioth which is thus the 19.1 I did follow the tutorial from LineageOS to build the 18.1 version which I probably shouldn't have.

As for LineageOS it's like a new kind of Elite closed open source thing, never saw that before.

Any recommendation, on getting started on my own, any reading, or should I just start reading commits logs and diff from LOS 18.1/19.1 of others devices that are supported ?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] LilBlinx:
Although it's old, still relevant. android_porting_guidebook
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
19.1 branch isn't ready to build, we are still working on it. you can see the latest changes only in gerrit. Will merge once its ready. You can only build 18.1 for now or pick changes from there. https://wiki.lineageos.org/how-to/using-gerrit
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Boracho:
eta?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] LmN101:
I flashed the lineage os recovery and tried to sideload lineage os however it complained about "package is for product alioth,aliothin but expected alioth". I'm new to custom roms on the poco f3 and I'm not sure what to do
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
Use lineageos-18.1 recovery to flash 19 for now. It will be fixed soon.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mattcri:
no indicator but i can se HD in the callscreen during calls
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
Vowifi is working for me.

One little problem: usb doesn't do any data stuff when the screen is off. This is sort of expected for security reasons of course, but when I connect the phone with screen off, then unlock the phone (this is not influenced by smart lock or whatever by the way , it really seems to be screen off) the phone charges but doesn't give the 'what do you want to do with this usb' prompt. Connecting the phone with the screen on and unlocked allows it to behave normally.

If I recall correctly, in LOS 18 the phone would show up as an empty mtp device (a phone device without a harddisk thing in it on windows).

This is quite annoying for trying to use Android Auto of course. Can anyone else say if they have this problem?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blopax3:
VOWIFI not working for me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] noraj1137:
The "Magisk in Recovery" methods is for phones which don't have a ramdisk but POCO F3 have a ramdisk.

The "Custom Recovery" is deprecated.

I want and I should use the proper "Patching Images" method.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fariaislam12:
It is a nice post.Thank you.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Doomkopf:
No issues faced ^^ By the way, in the part that you quoted, it says you can install Magisk via custom recovery if you *have* a ramdisk, not if you *don't have* a ramdisk ^^ And when you dont have a ramdisk, "Magisk has no choice but to hijack the recovery partition" (which is not the case here)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] noraj1137:
You are mistaking the "Magisk in Recovery" method (for devices that does not have ramdisk) and the "Custom Recovery" method (for devices that does have ramdisk but is DEPRECATED). I was right, you missread it.

I just tried the "Patching Images" method by extract boot.img from lineage-19.1-20220528-nightly-alioth-signed.zip and using payload dumper again and did exactly the same thing as for the stock ROM and it works well. Which is what Magisk dev call the proper method for Magisk 24.x.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Doomkopf:
Nah man, the thing is you brought up that "Magisk in Recovery". I was talking about flashing magisk using a recovery. You misread my first message.

Listen, do it like you want to. I don't really care ^^ Flashing it in lineage recovery always worked fine for me, and as long as it works fine, I'll continue doing it that way. Once I face any issues, I'll follow what the guide tells you to do in that situation and patch the boot.img.

Edit: Ah now I see what you meant, I did mistake it in my last message. Thats because I dont know much about Magisk in recovery mode. That's why I didn't talk about it in the first messsage, which you tried to say with the first sentence in your first answer. Anyways, happy flashing
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mathorv:
Hi, I am using your builds for many months now, these are flawless

I own lmi(f2 pro) and alioth

Used your for ih8sn build for alioth on lmi, did not do anything, however I would like you to ask few questions:

this build is for alioth(one signature) only or for lineageOS(ih8sn_lineage.zip)?

By the default .ps1 script installs 60-ih8sn.sh

How to revert it - I am not sure if it will survive recovery installation of lineageOS/mindthegappsgapps/magisk(in case of lmi/alioth)?

Would you consider adding Status bar cherry pick System>Status bar>Network traffic monitor from lmi?

I saw your previous tinkering with VoLTE, would it be possible to spoof phone model to mobile operator to enable VoLTE, like lmi pretending to be alioth? (without imei tinkering as this is illegal)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
Anyone?

I am suspecting that this commit here might be the culprit:

https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_sm8250/+/327352

usb: dwc3-msm: Set usb_data_enabled initial value earlier

Test: Boot with USB plugged in and have working USB data connection.

That's all well and good, and surprisingly my phone boots with usb working indeed. Problem I think is that there's a difference in how this code runs between when the phone doesn't experience a 'new plug in event' (when you boot with the cable plugged in) and the more important case of just trying to use Android Auto or even trying to read files off your phone (because if you plug in with the screen off, you don't get the notification to enable file transfer ever).

Moving that line around changes how the state machine works. There's a goto that would jump over the setting of the usb_data_enabled value before, but now that's not happening.

I don't really know that much about how these drivers work, but I hope that if this IS the issue, this might help? I'm just really annoyed with this problem, so if anyone can confirm the behavior (just connect the phone to a pc while it is sleeping, unlock, check if you get the notification to switch usb mode or not).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] althafvly:
Turn off Usb restrict in settings> privacy> Trust
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] hanzn:
Using the latest Gcam build seems to solve the issue:

[App] Mod Google Camera by B-S-G

Mod Google Camera by @B-S-G The latest version by B-S-G This post is about the mods created by @B-S-G. Here you will find instructions on how to use this port and how to configure it properly for yourself. Telegram public group BSG...

xdaforums.com

Tested it with pictures of hairy legs. Before the body hair looked like some weird blurry paste. Now the body hair looks sharp. I guess that's good :P
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] damonke:
I have tried this many times, but I don't think that toggle changed anything. It also mentions 'new usb gadgets' there right? Because that suggests that with this on, a registered android Auto device for example would still work.

Edit: I just tested the behavior of this toggle on my old LOS18 phone and windows makes the sound and connects and empty device in both cases.

I also think @CHGICEMAN has the same problem. I just checked the logcat he submitted in his Android Auto bug report and he has similar errors in there that I get:

05-19 18:00:20.551 I/android.hardware.usb@1.3-service-qti(839): Userspace turn off USB data signaling
05-19 18:00:20.551 W/android.hardware.usb@1.3-service-qti(839): Not able to turn off host mode
05-19 18:00:20.552 W/android.hardware.usb@1.3-service-qti(839): Not able to set Vbus state
05-19 18:00:20.554 I/adbd (1130): USB event: FUNCTIONFS_UNBIND
05-19 18:00:20.554 I/adbd (1130): UsbFfs: connection terminated: monitor thread finished
05-19 18:00:20.559 I/adbd (1130): UsbFfs: already offline
05-19 18:00:20.559 I/adbd (1130): destroying transport UsbFfs
05-19 18:00:20.559 I/adbd (1130): UsbFfsConnection being destroyed
05-19 18:00:20.580 I/adbd (1130): opening control endpoint /dev/usb-ffs/adb/ep0
05-19 18:00:20.581 I/adbd (1130): UsbFfsConnection constructed
05-19 18:00:20.323 I/ (0): read descriptors
05-19 18:00:20.583 I/adbd (1130): UsbFfs-monitor thread spawned
05-19 18:00:20.323 I/ (0): read strings
05-19 18:00:20.324 I/init (0): processing action (sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) from (/system/etc/init/hw/init.usb.configfs.rc:20)
05-19 18:00:20.328 I/init (0): Command 'symlink /config/usb_gadget/g1/functions/ffs.adb /config/usb_gadget/g1/configs/b.1/f1' action=sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1 (/system/etc/init/hw/init.usb.configfs.rc:22) took 0ms and failed: symlink() failed: File exists

I dunno, something goes wrong here and I feel like the problem is not with Android Auto itself, but something to do with that new USB stuff (this changed from los18>los19 right?).

EDIT: I have made a bugreport for this, because it seems that if the problem is where I think it is, it should not just be fixed for this device. https://gitlab.com/LineageOS/issues/android/-/issues/4780
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
There is a new MindTheGapps build: MindTheGapps-12.1.0-arm64-20220605_112439.zip . Everything is working fine at first sight.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] hanzn:
Should MindTheGapps being flashed when a new version is published and I don't have any issues?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] booci:
I do it but it is not mandatory because the apps update themselfs anyway
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] -GREY:
Do we have Network Traffic Monitor on LOS 19.1?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] noraj1137:
Poco F3 has no notification LED, so on MIUI there was the Always On notification system where you were able to enable a breathing color light on screen border when you have unread notifications. It seems there is not option on LineageOS. Any solutions?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] noraj1137:
Not by default at least.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] localbus:
Anyone has this weird alarm indicator on lock screen and status bar even there is no alarm set?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] friocasa:
Edited my message, the battery life in my case improved after several days. The stock rom(MIUI 13) still beats it, but the difference ain't that big. Since MIUI 12 had better battery life than 13, I guess that the best rom for battery life would be the Xiaomi EU one based on MIUI 12
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] neroes:
Hello, is your BT volume that low too? What can I do? Where can I change the region, for example (out of the EU / limits)

thx