yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] SharifOthman:
I'm here because I don't know what else to do.

I ordered a Pixel 7 from the official Google Store on October the 7th, received the phone on the 15th, and discovered right away that the rear cameras aren't working. I tried everything but it was clear it was a hardware issue. I called Google Support. They went through many steps to try and fix the issue but nothing worked. So I was prompted to get a replacement device. I sent my phone back on the same day with UPS, and 2 days later the phone reached its destination (I have a proof of delivery). And since then I got complete silence from Google.

I already talked to them twice, inquiring about the whereabouts of my replacement device, or the whole replacement process, but I got nothing. My RMA status page on the Google Store website is empty, doesn't show my returned phone nor my replacement device. Yesterday I went through the 3rd phone call with Google, was told that my case will be handled by the Pixel management team or so, and that I should hang up and wait for an answer from them later.

I just left off the chat with Google Support again. They told me that another agent is already working on the issue and that I should check my email. I haven't received any emails, of course.

It's been more than 2 weeks since I placed my order for this phone. Is this what I get for ordering their new device on the announcement day? And what other steps can I take in order to get my replacement device?
[Google Pixel 7] Ivixmax:
Same case than you but the problem was bubles beetween frame and screen.waiting for a solution.

1 week and no new notice.

i think someone is stealing packages or something between destination and the store or something.This is not normal...
[Google Pixel 7] SharifOthman:
May I ask where do you live? I'm in Germany and I've read on German forums a few successful RMA processes, but I have no idea why this is happening. If it's really stealing then it's not the customer'd fault, is it?
[Google Pixel 7] Keith W:
I am waiting on a full refund from Google for the Pixel 7 I had to send back with a dead screen.

They actually received the phone back within 24 hours but despite them having the phone back there has been a deafening silence for 5 days now.
[Google Pixel 7] SharifOthman:
I'm sorry about that. I hope you get your money back as soon as possible.
[Google Pixel 7] Ivixmax:
i am from Spain.and the phone was returned to Poland i think
[Google Pixel 7] SharifOthman:
My phone was also returned from Germany to Poland.
[Google Pixel 7] forever_lol:
Wow that's interesting cos Pixel is officially not released in Poland. That's why I ordered mine on Amazon Germany ;)
[Google Pixel 7] SharifOthman:
Now I wish I had done this :/
[Google Pixel 7] Keith W:
Still no refund and Google support has been of no support.

I have called them twice now in as many days chasing this up, spend ages on hold whilst they "check things" only to then be told it has been escalated to a higher tier of support and they will email within the day and to wait until I get the email - I have heard that line twice now in as many days.

I have told them if they have mislaid the phone or it has gone walkabout then that is not my problem - I have signed proof they got it back
[Google Pixel 7] hammered58:
Get the credit card company involved see what they say,
[Google Pixel 7] TonikJDK:
Be careful disputing the charges. Google has deactivated the associated account of people that have done that in the past. Everything just goes poof.

Use that as a last resort.

Hit up @MadeByGoogle on Twitter. They will engage you via DM. I have had good luck with that method.
[Google Pixel 7] Keith W:
I have actually been doing that today and they are just as useless.

First they tried to send me back to phone support after I told them I had tried that twice already

Then they asked me to send the details over via DM only for them to then tell me the same as phone support "We have escalated to one of our specialists who will investigate and be in touch via email" - no one gets in touch, no emails, nothing.

Totally useless.
[Google Pixel 7] Ivixmax:
Finally google returns me the money today.15 days to finish the nightmare.So patetic
[Google Pixel 7] Keith W:
Good to hear you finally got your money back.

It should not have taken that long though.
[Google Pixel 7] bobbarker2:
Google store has notoriously terrible support. Just the other day they literally told me to go take my business elsewhere because I wanted to get a pixel 7 pro.

A friend of mine once ordered a pixel phone and he got a pixel box with no phone in it. He spent hours trying to prove it and work it out, the shipping weight was off so there was hard of it and right there, but Google refused to do anything. Lost a customer for life over that.

Just a general FYI, if you RMA anything with almost any company using the device's warranty, the replacement is "refurbished” i.e not brand new.
[Google Pixel 7] Keith W:
Yes I had that happen before with them trying to fob me off with a refurb in exchange for a phone which was just weeks old.

This time I told them I just wanted a full refund as I only had the phone 3 days before the screen up and died on me.

I had issues with the P6 and now issues with the P7

This whole thing has left a real bad taste in my mouth and I can not see my self buying another Google product again after this.
[Google Pixel 7] bobbarker2:
Yep, the only reason I bought my phone through Google was the store credit + Google One 10% and even then I was crossing my fingers hoping nothing was wrong with it because I know first hand and second hand what a nightmare it is to deal with their Store support. I think the phrase "Too Big to Care" applies to Google.

I could have gone to Best Buy and gotten a $200 credit there (same phone trade in value offered as Google Store) and in retrospect, I probably should have done that since Google Store only offers overpriced accessories ($90 for a Wireless stand charger!?)
[Google Pixel 7] Finneri:
Let me get this right. You sent the phone back on 15th and it took 2 days to ship (17th?). And you got your money back 25th? Which means your phone was in support center for just over a week?

For me this is totally normal, never got my phone back in one week if it needed maintenance.

And I know that Google can be a piece of fieces, I've fought with them about my Pixel 3 for 5 months. That was long. Week? Nah bro, you're fine.
[Google Pixel 7] Ivixmax:
No.no and no
[Redmi Note 10 Pro] GX Ely:
Hello guys,

i want to made a MIUI 13 China Stable port for Redmi Note 10 Pro (sweet). A port already exists, but is buggy. How i can made a port with 0 bugs?
[Touch Cruise General] yorkshiresurfer:
Hi,

Just upgraded from my Orbit to an Orbit 2.

Having problems connecting to the Internet at home using the Wifi connection.

The phone sees my home wireless ( 3 full green bars ) but will not physically connect to it.

Did not have this problem on my old XDA.

It connects no problem using the data connection - but i want to use the fast wifi at home.

Spent a frustrating 4 hours last night trying to sort this - without success !
[Touch Cruise General] wafupilot:
I had a similar problem. Try deleting the partnership with your wifi in the connections settings, soft reset and try again.
[Touch Cruise General] fallenmonk:
Will give it a go.
[Google Pixel 7 Pro] Bxperiaz3:
Been enjoying the pixel 7 pro so far. Sadly one repeated issue I'm having is the phone just completely dropping service randomly from time to time? I'll go from full 4G to no network at all in the space of a few seconds. Apparently this is a known issue on some devices. Does anyone know of some type or fix or am I looking at returning the phone?
[Google Pixel 7 Pro] joshtb86:
I've seen it happen a few times but it's been so rare that honestly it is not affected my usage of the phone
[Google Pixel 7 Pro] Bxperiaz3:
Mine is pretty often but I'm on an esim so maybe that's the issue
[Google Pixel 7 Pro] joshtb86:
Interesting, I'm on physical
[Google Pixel 7 Pro] MoneyNotEnough:
I guess the only way to resolve this is for you to get a physical sim and test it out.
[Google Pixel 7 Pro] EtherealRemnant:
Not having this issue on pSIM or eSIM. Signal is rock solid on mine (and actually got a bit more solid on the beta but was already great out of the box after the first OTA).
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
MUST-READ BACKGROUND - Android 13 and the two approaches:

As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.

Since PHH made up his mind, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs.

Meanwhile, I'm aware that at least I myself am not as capable as PHH, and won't be able to look after the myriad of patches and devices, esp. legacy ones (pre-A10). Therefore, inspired by @PeterCxy , I'm taking a different approach - start over from AOSP's generic gsi_* target, add in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process and making it easier for myself to follow/maintain. This is a radical, selfish approach that by definition won't work for legacy devices anymore, and won't work as well as PHH-based GSIs that you've come to love either. However, I've fixed it up to my own daily-driver standards, and I figured it should still be of use to many. For now, I call this the "light" approach.

Disclaimer:

No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.

No guarantees that everything would work. This is a GSI, bugs are bound to happen.

The selfish nature of this approach means I can and will ignore certain bugs as I see fit. Deal with it or kindly go try something else.

Download:

https://sourceforge.net/projects/andyyan-gsi/files/

Scroll down for the naming rules of variants.

Compressed as .xz archives - extract first.

Stuff on GitHub (builders-only):

Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.

lineage_build_unified - my unified script for building

lineage_patches_unified - my unified patches for building

device_lineage_gsi - my device tree that extends native generic targets

Thanks to:

The LineageOS team - helping me out even when they don't offer GSIs themselves

@phhusson - shaped the treble community, and even the "light" approach uses his fixes/infra extensively

@PeterCxy - inspired me with his personal-use GSI, and coded critical fixes such as sysbta

...and more

Donate?

https://paypal.me/AndyCGYan
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This post documents my progress on top of the native generic targets.

Already implemented/fixed:

Built-in root (PHH-SU)

Device overlays

Screen resolution & refresh rate - improved upon PHH's implementation

Alternative audio policy (Qualcomm)

Disable soundvolume effect (Qualcomm)

Alternative backlight scale (MediaTek)

resetprop/copyprop tool

In-call audio

BT audio

VoLTE on Qualcomm/MediaTek pre-S vendors

VoLTE on Qualcomm/MediaTek S vendors - new, backported to PHH-based

GAPPS - using MindTheGapps for now

Securized - "on-demand" reversible toggle

Disable A2DP offload

Alternative audio jack detection

Signature spoofing - limited to priv-app for the same security reason as in PHH/TD-based

Optional FP lockout (set persist.sys.fp.lockouts.disable to true to disable timeout on failed FP attempts)

Built-in PHH-SU app for *S variant

Override minimum brightness

Override navbar availability

Exfat

In-call audio on Snapdragon 8 Gen 2 (SM8550) and newer Qualcomm devices

To be implemented/fixed at a later time:

VoLTE on Motorola Qualcomm S vendors - situation did not improve with stock T, lowering priority

Known but will not implement/fix:

Compatibility with legacy (pre-A10) devices, A-only, VNDKLite

FOD/UDFPS (commonly known as in-display fingerprint) - not skilled enough for it and not interested either

MediaTek kernel BPF bug (#9)

VoLTE on non-Qualcomm/MediaTek vendors

Samsung/Huawei oddities
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Notes:

I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.

No A-only or VNDKLite builds. These are concepts that don't exist natively.

GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.

ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.

Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.

Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
[Treble-Enabled Device Development A/AB ROMS] Melovespa:
Good job!
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
Yay!!!
[Treble-Enabled Device Development A/AB ROMS] a9381:
yay!!!! thank you!!!!
[Treble-Enabled Device Development A/AB ROMS] a9381:
Thank you very much for your great work. I've been waiting for this for a long time.

I ran into a very, very strange bug.

I have a Qin F21PRO (MT6761).

This model has two sub-models:

4GB RAM + 64GB storage

3GB RAM + 32GB storage.

My device is

4GB RAM + 64GB storage

But after flashing this GSI, it is shown that there is only 32GB storage.

edit: after factory reset via twrp, i getting 64GB storage
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
There's a known kernel bug in some recent MTK devices that breaks BPF badly, resulting in broken networking features since Android 13, and no-boot since r11 (Google decided to tighten the check). I've reverted the no-boot, but the actual bug can't be fixed from platform-side.

This affects LOS in that it has Restricted Networking Mode turned on by default, and with the bug in place, apps cannot be added to the allow list, resulting in no internet in even system apps.

If you own an MTK device and notice such a thing, as a temporary workaround, you can turn the feature off manually with:

adb shell settings put global restricted_networking_mode 0

If you're on the gN variant, SetupWizard would also have no internet, so just skip the setup entirely, turn on USB Debugging once you're in the OS, run the above, then re-initiate the setup from the status bar.

As for a more persistent fix - thanks to @Rortiz2 , there's now a way to manually patch the kernel binary, however I no longer have an affected device for testing this. Feel free to try out the patcher here.

There might be other broken networking features that I'm unaware of. In the long term, the one true solution is to upgrade to a newer vendor base, hoping that the OEM has merged the kernel-side fix.
[Treble-Enabled Device Development A/AB ROMS] redymedan:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.

If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
[Treble-Enabled Device Development A/AB ROMS] spider1163:
Same problem with Redmi Note 10 (mojito)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@redymedan @spider1163 Can you give me the full result of "getprop" from shell? Paste it to e.g. Pastebin.
[Treble-Enabled Device Development A/AB ROMS] redymedan:
D

Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled. also in Gesture menu "System navigation" option appeared. It works now on my Galaxy A50, Thanks :)

Other problem: Google Play Protect certified "This device isn't Play Protect certified"

View attachment 5742611
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
amazing! waiting for gapps variant now.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Thanks for confirming it's that simple! Given that "light" won't look back on legacy devices, I think I'll just enable this prop globally in the next releases.
[Treble-Enabled Device Development A/AB ROMS] AngelCastillo029:
This is exactly what I was waiting for, it will be fun to test on my old Huawei P smart 2019 with Android 9 vendor so let's see what happens. Any result of this experiment will be shared here.
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
THX for your great work.

But how can I install gapps?

I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.

There's no working TWRP for my device:cry:
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
you wait... :)..
[Treble-Enabled Device Development A/AB ROMS] kernel_t4sk:
THX for your great work. but auto brightness not working Is this expected behavior？
[Treble-Enabled Device Development A/AB ROMS] Sofian75:
Wifi is working for me but I can't get internet to work.

What vbmeta file did you use?
[Treble-Enabled Device Development A/AB ROMS] tavoc:
For Internet you have to Follow the Instruction on the first page regarding mediatek and network

shell settings put global restricted_networking_mode

I used the vbmeta from the official android 11
[Treble-Enabled Device Development A/AB ROMS] Sofian75:
That's it, thanks.
[Treble-Enabled Device Development A/AB ROMS] tavoc:
And you don't experience constant WiFi drops? Did you flash before the clean vendor ROM?
[Treble-Enabled Device Development A/AB ROMS] Sofian75:
Never had problem with the wifi, not even with the stock ROM.

I flashed vbmeta and vbmeta_vendor but I don't know if it did anything.
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Finally it booted on my OnePlus nord 100 phone, it works perfectly fine but there is no OnePlus DT2W😢
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
1. Is it worth to spend time on fixing freezer? I have v1, but gsi is using v2

I'm thinking about manually creating files like in freezer v2 and script which will be between these files and freezer v1.

2. Is it worth to build gsi with optimization for specific cpu?
[Treble-Enabled Device Development A/AB ROMS] Amusing3-Bolster-Stitch:
Is this a bug anyone else has experienced -- setting the Wallpaper via Settings (Wallpaper & style) will often lead to the default Lineage background (teal gradient) being applied, instead of the wallpaper. Workaround is to apply the wallpaper via a gallery viewer.
[Treble-Enabled Device Development A/AB ROMS] Amusing3-Bolster-Stitch:
Also, another small bug -- the kernel power management settings seem to prevent the Sony adapter/charger (30W that comes with the phone) from charging the device. But another power adapter works fine or another custom kernel with Sony power management features. I think this is probably because the Sony charger requires a specific response from the device power management feature in order to sustain the charging.
[Treble-Enabled Device Development A/AB ROMS] Hnojohn:
Thank you For this awesome rom, i was wondering if how i can fix this issue of mine in every gsi rom that my cpu cores would just run at 500-700mhz at most times resulting very laggy ui animation/transition, also there's time when it runs at 1200-1500ghz it become smooth then goes back at being sluggish again. Any help is appreciated
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
maybe you could use a kernel manager to try set the governer to something else
[Treble-Enabled Device Development A/AB ROMS] Pervokur:
input boost can help

echo > "0:1305600 4:1401600" /sys/module/cpu_boost/parameters/input_boost_freq
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Google hasn't released QPR2 or security patches yet - this month's update will be postponed until one of them drops.

As of yesterday I've figured out in-call audio on Snapdragon 8 Gen 2 (SM8550) devices, however I can't publish it just yet. It'll be in a future build when ready.
[Treble-Enabled Device Development A/AB ROMS] mrhamed:
Does it work on M30LTE (SM-M305F) device?!
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
try it out.
[Treble-Enabled Device Development A/AB ROMS] reisyreinier:
Any guide to flash this image on xiaomi redmi note 11 4g(selene) or similar?
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Lineage add some prebuild apk for webview..and now you must configure git lfs
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]

As usual with "feature drops", things can change or break majorly. I had to amend my personal changes quite a bit, and I've uploaded an updated personal build to match.

Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11 and ░░░░ ░░░░ ░░ ░░░, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too.

Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.

Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.

Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.

And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:

rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*
[Treble-Enabled Device Development A/AB ROMS] uschipower:
I am a beginner in GSI, so sorry for my question.

What is the difference between AndyYan's "LOS 20 TD-based" and "LOS 20 light"?

When should I choose the first, when the other?

Thanks.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Have you read both OPs yet, or are you looking for a TL;DR?
[Treble-Enabled Device Development A/AB ROMS] reisyreinier:
The answer is in OP, but shorting, light is a from scratch version build by Andy with no support to older devices. TD-based is a continuation of @phhusson work by project treble developers. I choose light, but if you have an older device or want to kept @phhusson functionality, select TD.