yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] coal686:
Oh hai!, especially miggsr, it's been a while my friend.

This debate is very interesting, but I think it's run its course. Substratum can cause problems on a phone. Duh. Everything on this site can cause problems on your phone. That's the whole point of XDA! To learn, to push devices to their limits.

Android would be nowhere near as awesome had they not kanged all the good ideas from the developers at XDA. You couldn't even restart a phone on stock Android back in the day, only shutdown. XDA people added it to their custom ROMs and magically it was added by Google.

As for trust, and overlays, and keylogging, and such, again, that can happen on almost anything here. I've flashed plenty of custom ROMs in my day, but only did so from trusted sources. Because I'm basically trusting that developer to do the right thing and trusting the community will point out when they aren't.

Pixel Tweaks might have trouble on the Pixel 6. Not surprising, the device is brand new as is Android 12. The developer is fixing what needs fixing and helping people figure out what's wrong with their device when Pixel Tweaks isn't the problem. Great! Just what we hope XDA is used for.

So, let's move on from the debate about Substratum Lite and continue focusing on Pixel Tweaks. If you want to discuss the merits of Substratum for this device, please create your own thread somewhere else.

I'm subscribing to this thread so please let's be on our best behavior. If you have any questions or concerns, feel free to send me a PM.

Thanks,

coal686

Senior Moderator
[Google Pixel 6 Pro] miggsr:
🤯🤯🤯🤯 Holy hell I haven't seen you in years!! Good to you are still around. As you can see I've moved on to better devices (IMO) than HTC LoL. Seeing that name @coal686 is definitely a blast from the past.
[Google Pixel 6 Pro] Oswald Boelcke:
Moderator Announcement

Thread preliminarily closed due to moderator's investigation and maintenance.

Thread re-opened. Please refer to @coal686's post above.

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 6 Pro] eg1122:
I have the mod ready for December OTA. I'll post once it's been tested by some of my testers since I don't have a pixel 5. Hopefully this resolved the issues you had.
[Google Pixel 6 Pro] eg1122:
What version of Android Auto are you guys using? I know it has been rewritten differently on Android 12 and I don't have an app icon to launch it (I never use it). It shows as installed from play store just not sure how to access it now. Maps has something similar to how I remember Android Auto and that works for me but I don't think you guys are talking about that.
[Google Pixel 6 Pro] gettinwicked:
version 7.0.614134-release

It's the latest. They changed it from an app to more of a service. It can't be launched via app anymore, it's either automatic when connected to a car, it by Google assistant.
[Google Pixel 6 Pro] mattstermh:
I just installed this and upon rebooting I get the G logo and it just keeps rebooting
[Google Pixel 6 Pro] elong7681:
If you are on the December update that would be why. It has not been updated yet.
[Google Pixel 6 Pro] eg1122:
Nvm...........
[Google Pixel 6 Pro] eg1122:
The mod posted is for November ota for pixel 6/6 pro. The ones on post #4 is for November ota for older pixels. An update is required for the December OTA, I will release it within the next day or two. Also could you please let me know which device you are on and on which security patch you are on?
[Google Pixel 6 Pro] mattstermh:
I'm on Pixel 5 with the latest December update.

What can I do to get my device back to working for now?
[Google Pixel 6 Pro] eg1122:
Boot into safe mode. Do this rebooting as soon as you see the G logo press and hold the volume down button until phone boots into os. Once in safe mode do a regular reboot. You will boot up with all Magisk modules disabled.
[Google Pixel 6 Pro] mattstermh:
Ok ty, and how will I remove this module and install the new one when it's released?
[Google Pixel 6 Pro] miggsr:
After the device loads safe mode reboot again. Once it's booted all magisk modules will be disabled. Just click the delete module option in magisk. Reboot and that's it. Once the Dev gets the see the December update for Pixel 6 pro I think 🤔 he might be able to fix it.
[Google Pixel 6 Pro] elong7681:
Did you even read the OP because it would have saved you from the problem you have and would answer the question as to how to install the update. Reading the OP and the thread is your best friend and if you still have a questions then feel free to ask.
[Google Pixel 6 Pro] mattstermh:
thanks, i'm good for now
[Google Pixel 6 Pro] eg1122:
Once it has been disabled you can remove via Magisk without having to enable it.
[Google Pixel 6 Pro] mattstermh:
is there something released for the latest update to change the ugly clock on both the home screen and the even weirder clock on the lock screen?
[Google Pixel 6 Pro] eg1122:
Maybe from someone else. My tester just reported back with an issue with the December files. Going to fix that before releasing it.
[Google Pixel 6 Pro] eg1122:
Post 4 has been updated for older pixel models that received December OTA
[Google Pixel 6 Pro] mattstermh:
Just installed the update.

When I open substratum lite it says please allow root access permission
[Google Pixel 6 Pro] miggsr:
For any of these mods to work correctly you would need a route is your device currently rooted do you have magisk installed correctly
[Google Pixel 6 Pro] mattstermh:
Yeah, I have magisk installed and applied some other modules earlier today without a problem (for example, centered clock).
[Google Pixel 6 Pro] eg1122:
Substratum Lite requires root access to function properly. Do note that this mod will not work with any other mod that edits systemui (center clock lives here), framework res, and pixel launcher.
[Google Pixel 6 Pro] miggsr:
But is this the first time you're opening substratum light?
[Google Pixel 6 Pro] mattstermh:
yes. My device is rooted - not sure what the issue is
[Google Pixel 6 Pro] miggsr:
There is no issue...that's the issue... Anytime an app that requires root permissions, you're going to get that request from an app substratum requires root hence the notification for requiring root popped up. Now I will tell you that is not related to the mod on this thread. But the mod in this thread does require root as well.
[Google Pixel 6 Pro] eg1122:
Open Magisk, click on Superuser tab at the bottom and see if substratum lite has root access.
[Google Pixel 6 Pro] mattstermh:
The superuser list is empty - that must be it

edit: ya that fixed it ty
[Google Pixel 6 Pro] mattstermh:
actually, lol, it says 'installed root system is not supported. substratum lite only fully support latest stable magisk version (i am on canary)
[Google Pixel 6 Pro] eg1122:
You need to grant access to substratum lite when you open it. If it doesn't prompt you for access and the list is empty then clear substratum lites data and open it again.
[Google Pixel 6 Pro] eg1122:
I'm on latest Canary as well. Make sure you have substratum lite installed and not substratum.
[Google Pixel 6 Pro] mattstermh:
I do
[Google Pixel 6 Pro] mattstermh:
idk what happened, just re-isntalled and that fixed it. seems to be working
[Google Pixel 6 Pro] eg1122:
Good. Just a warning, you mentioned you installed a center clock module, if you want to use this mod you need to uninstall that, reboot then flash this mod. If you flash this mod over the mod you have you will probably get a FC or a bootloop.
[Google Pixel 6 Pro] mattstermh:
Done, thanks. I don't see Pixel tweaks in substratum lite despite adding the module but I am going to try and figure out why.

edit: figured it out. Somehow using the apk instead of the zip files was needed... unless they are not the same
[Google Pixel 6 Pro] eg1122:
You need to install the app as well. Its in post #3
[Google Pixel 6 Pro] mattstermh:
yeah that did the trick
[Google Pixel 6 Pro] mattstermh:
Got everything working
[Google Pixel 6 Pro] eg1122:
I got the December zips ready...but since we can't root the December ota I'm going to hold off on release until we get an update from Magisk. Also, this release will not include a fix for Android Auto. but as soon as we get root on december ota I will jump on that issue.
[Google Pixel 6 Pro] eg1122:
Since there is a workaround for root now I have released the December OTA update.

Changelog​

Pixel.Tweaks.Helper.v2.0.0.5

December 2021 OTA Update

Renamed Files to make file names shorter

- Pixel.Tweaks is now PT

- Searchbar.Removal is now SBR

Pixel Tweaks v6.4

Reworked the app drawer search removal as the previous method no longer worked.
[Google Pixel 6 Pro] gettinwicked:
@eg1122

Did you happen too figure out the Android auto issue?

Thanks again for your great work!
[Google Pixel 6 Pro] eg1122:
Not yet. I was busy all day and just managed to port over the mods to the December update. I will look into it tomorrow. My attention is 100% set on fixing that now and will release an update as soon as it's taken care of. I might hit you up tomorrow because apparently my truck is not listed as compatible with Android Auto (according to their site). But I will try to troubleshoot as much as possible on my end before reaching out.
[Google Pixel 6 Pro] banshee28:
Hi, so I think I had most of this working fine. I then had a bright idea to install Nova launcher and reboot! LOL

Now i cant boot. Safeboot does not work either. Is there a way I can boot enough to get adb working so I can remove nova and get it to boot?
[Google Pixel 6 Pro] gettinwicked:
Okay, awesome! I'd be happy to test AA.
[Google Pixel 6 Pro] eg1122:
One of my testers had a similar experience not being able to enter safe mode. He successfully entered by completely shutting down the phone then turning it on. Once you see the G on the screen press and hold volume down until it boots. If you have usb debugging enabled and can get adb connectivity during the bootloop, you can try the following command to remove all modules.

adb wait-for-device shell magisk --remove-modules
[Google Pixel 6 Pro] banshee28:
Nice, so I did try just that previously but could only get the command pasted then it rebooted and never seemed to take effect. Will try again.
[Google Pixel 6 Pro] eg1122:
If anyone is willing to help narrow down the Android Auto issue please flash the zips bellow. You need to be on the December OTA.

For Pixel 6 series use Pixel6Test zips

For older pixels use Pixel5Test zips

You will need to remove Pixel Tweaks completely (magisk module and substratum overlays), reboot, and then flash Test1.

After flashing Test1, reboot and check Android Auto, if it crashes no need to flash Test2 or Test3 and just let me know Test1 broke it. If its working flash Test2 over Test1 and reboot. Same thing if it crashes let me know Test2 broke it, otherwise continue to Test3

Thank you in advance. This will let me know which part of the mod has the issue and I will be able to focus on that.
[Google Pixel 6 Pro] banshee28:
Tried several times now, it tires to boot then reboots. Did the Nova Launcher prob break this? Is my only option to re-flash factory image?
[Google Pixel 6 Pro] eg1122:
Not sure how Nova would do this. must be a weird combination of it and my mod. Never had anyone experience this so not really sure what is going on. You could try flashing stock boot.img (removes root, therefore no modules load up), boot up and uninstall Nova then flash the patched boot.img again.

If you don't want to flash the stock boot.img you can boot it to temporarily loose root with the following command in fastboot.

fastboot boot boot.img

boot.img being the stock boot.img.

If you are able to boot up you will regain root on the next reboot.
[Google Pixel 6 Pro] eg1122:
So just realized Google changed up the colors with December ota. Once I figure out the Android Auto issue I will try to make the colors accurate again.
[Google Pixel 6 Pro] cd993:
Can I ask what the stock icon size is? I'd like them a little smaller but rather than some trial and error be handy to know what the default size is for a reference point. Many thanks in advance
[Google Pixel 6 Pro] mattstermh:
Only some of my apps utilize the navbar/gesture colors applied from System UI. Was working fine, then I changed it. Hmm
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Hello,

Finally I found a GSI ROM on which it is possible to enable VoLTE.

(thanks to @hackintosh5 )

Most users will be disappointed because it's a GSI based on A9 Pie and requires stock EMUI 8. (I don't think it's important, higher isn't always better...),

Tested ROM: Havoc-2.9-aonly . More information about Havoc can be found here

(inc. download link, guide, TWRP etc.)

For those who want to try it:

- be sure your phone is running EMUI 8

- Flash Havoc

- Download HWIms.zip magisk module

https://mega.nz/file/lt0VkaDY#hou-mruVYi1yp2MmUxzDukloTdttjn1X0kIbQGw4LDY

- Install TWRP

- Flash Magisk v20.3.zip in TWRP and install Magisk manager apk.

- In Magisk manager install HWIms.zip module

- Reboot .

Note: Thanks to Oreo VoLTE can be enabled also by installing "VoLTE-FIX-A11-hi6250.zip" by @DarkJoker360 in TWRP (without VoLTE icon in status bar)

Download

Note 2: If all this has worked on my device, it does not mean that it goes with everyone else.

Maybe it works on other a-only ROMs. I tried EvolutionX A, PixelExperience_Plus 9.0 A, etc. but couldn't boot them.

Screenshots:

View attachment 5447761

View attachment 5447801

View attachment 5447803

View attachment 5448185

Update: tried on EMUI 9.1 , LOSQ v224, no luck...

View attachment 5447943
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Hi!

How are perfomance and battery life?

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Hi, honestly, I haven't tested perfomance and battery life or any other criteria, but it's certainly not worse than on a stock rom (as well as all custom ROMs on A8).
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Hi!

I built a lineage 16 gsi for emui 8, could you please test if boot and if volte works too?

GSI lineageos 16 EMUI 8 october patch 2021

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Hello dev :) , it boot and VoLTE works too.

The mentioned Magisk module does not work (is it really GSI? ). But thanks to Oreo VoLTE can be enabled by installing "VoLTE-FIX-A11-hi6250.zip" by @DarkJoker360 in TWRP (without VoLTE icon in status bar).

P.S.: browser doesn't work due to missing webview, but it can be easily fixed ->

https://xdaforums.com/t/rom-official-anne-9-lineageos-16-0.4151163/post-85010583

P.S.: This is just my experience on ANE-LX1 8.0.0.178 (C432).
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Hi!

Thanks for testing! I will fix webview on the next update! Yes is a gsi with @AndyYan patches so is strange that module is not working. However I will try to integrate that fix on gsi. Is fully working (nfc, GPS)?

Edit: I'm not a dev, just a maker 🙂

What is the error on magisk module?

Cheers
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Hi!

New update is online! if someone is interested i will open a new thread and i will continue upload new images. Basically is a gsi with some dropped samsung patches.

GSI lineageos 16 EMUI 8 November patch 2021

Changelog :

Fixed webview

November security patch

I'm also upstreaming Labyrinth kernel.

Let me know if all is working good and if you want a new thread with regular updates!

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Sadly, most people want to install a Custom based on the latest Android version, even if the lower one works better :rolleyes:.
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
It works like a charm :)

this relates to P8 lite (2017), if I'm not mistaken...
[Huawei P20 Lite Guides, News, & Discussion] TureX:
HI!

Labyrinth is for hi6250, should works on p20 lite too.

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
I know, tried Labyrinth & Labyrinth_mod some time ago. ANE cannot boot with this kernel, tested on Oreo/Pie , Stock/GSI. Maybe I'm just unlucky or there's a problem with my device.

I think only two custom Kernels work on EMUI 9 - your Phenix and Papaya-v1.6.
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Did you tried my last Labyrinth version?

I published a 4.4.230 version with security level patched(kernel doesn't boot with 2018-11 but seems OK with 2018-07 security level patch) and modem driver compatible with last baseband.

I have finished up streaming to 4.4.291 but I didn't publish because I was attempting for a feed back on Labyrinth thread(but no one give me feedback).

Edit : is only for emui 8
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Of course, doesn't work.

Only Labyrinth v1.2 and rev1.3 worked for me (on Custom ROM) with SELinux enforcing & MorfuZ Kernel v5.6. with SELinux permissive (on Stock and Custom ROM).

Edit: P20 Lite
[Huawei P20 Lite Guides, News, & Discussion] TureX:
HI!

Thanks for the feed back. Could you please send me pstore log?

About the volte icon, is missing on lineage, I will try to add in the next update( or maybe is better hiding for notch?)

Edit: kernel is just bootlooping on splash or give you errors on fastboot?

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
I'm sorry, but I'm tired of being your private tester. When I wanted to test custom A10, A11 a year ago, I bought a used phone, I don't borrow it from my neighbor...
[Huawei P20 Lite Guides, News, & Discussion] TureX:
Man, I don't want you as mine tester... I'm sorry if you feel this. I just ask in a public forum, I never tell you to do test first.

However, maybe we are only you and me to use custom thinks so Is maybe time to stop publish. If I can test, I will publish again. Have a good day!

Cheers
[Huawei P20 Lite Guides, News, & Discussion] -Alf-:
Apparently I misunderstood your post above, sorry.
[Huawei P20 Lite Guides, News, & Discussion] AltairFR:
Does this lineage work under EMUI8 (Prague) ?
[Huawei P20 Lite Guides, News, & Discussion] TureX:
HI!

Yes, is an a-only gsi

Cheers
[Huawei P20 Lite Guides, News, & Discussion] AltairFR:
I would look, on my side I rather develop under lineage 18
[AT&T Samsung Galaxy S8 Questions & Answers] willnotbecontrolled:
Hello,

I am new to this site, and have a burning question I am trying to find an answer for.

So AT&T has been my carrier since about 2014. In July of 2019, I purchased an unlocked S8 from Amazon for about $350 Description says it is: Samsung Galaxy S8 64GB Factory Unlocked Smartphone - US Version (Midnight Black) - US Warranty - [SM-G950UZKAXAA]. In the settings, the model number is listed as: SM-G950U1.

Recently, I received a message from AT&T saying that they are shutting down their 3G network in February of 2022, and that my phone will no longer work on their network. I went into one of their stores and showed them that my phone operates on LTE, but I was told that is for data only and voice operates on 3G. I could not remember the VoLTE name at the time, but mentioned that my phone had the capability to operate on LTE. They refused to go thru settings with me, and told me that my phone will stop working in February. Period. End of story. Also, I was told the same thing that the message states, that they are sending me a new phone and will be deactivating my phone after 30 days.

Now some of my friends are laughing at me saying, "Dang free phones!" But I do not want a 5G phone (which is obviously what they are sending). I have my reasons and this is not what I wish to discuss here.

The issue is... I love my telephone!! It does exactly what I want, and I don't need anything new. Not to mention that I paid for it entirely, with no subsidy from AT&T. I specifically bought it unlocked with intentions of avoiding contracts and having the ability to switch carriers if I so choose.

I am pretty sure that I saw VoLTE mentioned in my settings a while back. But now a search on my phone finds nothing. I assume a firmware update hid this info from me.

So... what gives? Does anybody here know if this particular device can make/receive voice calls using VoLTE - on AT&T (or any other carriers) - simply by changing settings in the phone? Do I have any options to make my phone continue to operate as intended? With any carrier?

Sorry for the long post. Any advice would be greatly appreciated.

Sincerely,

Steve
[AT&T Samsung Galaxy S8 Questions & Answers] djmdesign:
Same issue with crickett (att).

got that txt msg, recently maybe december there was a firmware update that greyed out my network settings and hid some items.

i cant even change my prefered network, 3g 4g lte etc, its locked..

I have the 950u1 also

HOWEVER I have a s8 950U that I think has all these unlocked.

Im going to backup and odin flash the U firmware to the UI and see if it works.

Thats bull**** about doing this. greedy ****s..

I go with somone else if I have to.
[AT&T Samsung Galaxy S8 Questions & Answers] djmdesign:
press phone icon, then top right corner hit the 3 vertical dots.

select settings and it should be in there if you havent updated lately... they ****ed us and locked out network and volte settings.
[AT&T Samsung Galaxy S8 Questions & Answers] willnotbecontrolled:
Please let me know if this works. I thought about doing the same thing, but have not gotten around to trying it. In theory, it sounds like a solid plan. But I have a couple of concerns.

During a recent phone call, AT&T told me their system has flagged my IMEI and that my phone will stop working very soon. So, if the system flagged an IMEI as an unsupported device, will it even matter which firmware is installed? Or will their system just deactivate the phone at some point?

Second, if you install the 950U firmware in place of the 950U1, will the device become carrier locked at this point? That would really suck if it did.

BTW, I was able to lock preferred network to “LTE only” by dialing *#*#4636#*#* and entering Device information screen. Unfortunately, my phone would not complete a call when using LTE only setting. VoLTE provisioned toggle is greyed out, along with others. Seems to me that if a guy could self provision VoLTE, this would solve the issue.

I called AT&T tech support and spent 45 minutes trying to get them to provision VoLTE, but they could not, or would not do it. At first, they kept telling me that my phone is a 3G phone. I argued that I could change the radio to “LTE only” and that my sim card status showed LTE for “mobile voice network type”, which proves that the phone is indeed LTE capable for voice calls - but that it will not complete a call because it is not provisioned to do so. Eventually they told me that their system would not allow them to provision VoLTE for me, since it is flagged as an unsupported device. Which leads back to the first part of this post.

I also found some stuff on reddit about putting the phone into “engineering mode” and something about a Samsung tool that unlocks additional dialer codes. Have not tried this, tho.

At this point, I am just completely fed up with AT&T for this whole S8 situation, as well as other unrelated issues. I will most likely switch carriers for principle’s sake, even though I know other carriers play similar games.

Anyway, I am interested in whether or not you find a solution and would very much like to hear about it. Thank you for the response!!
[AT&T Samsung Galaxy S8 Questions & Answers] willnotbecontrolled:
Yep... AT&T is full of it. I got sick of wasting my time and energy trying to fight this. I eventually just switched over to TMo, and I have been running around with my S8's radio set to LTE only. No issues whatsoever. Great cell service, $30 bucks a month cheaper, all fees included in the flat rate, and a free Netflix account, to boot.

See ya AT&T!!! I hope some group with the the gumption and time takes you to court for your deceptive trade practices. I hope you lose lots of customers, time, and money for your douchery!!!