yashsingh1/xdaforums huggingface dataset:
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Az.az1:
Wifi reception in this ROM is very weak. Please fix it

Edit : I do not recommend this ROM.. With use for less than a month, the phone has become very slow and turns off automatically and applications stop and do not work until you turn off the device and turn it on again.. and there is a problem with the camera, the flash precedes taking the picture The result is a dark image ..
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Nayem Ur Rahman Durjoy:
please..need a overclocked kernel for poco m2...it will help gamers..
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Nomad911210:
Problem with camera app when i do photo with flashlight
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Lolbit723:
does anyone have version 2.1 of this rom? i unfortunetly deleted mine, but i wanna go back to that version as android 13 isnt my thing
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Istiaqe:
Can't download from pling.....can anyone help me with that.....I want to install this romView attachment 5859263
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] bicho2015:
Project Elixir [Custom ROM] - Browse /thirteen/lava at SourceForge.net

Project Elixir basically offers a minimal UI enhancement & close to Stock Android ROM with great performance, security and stability. Your…

sourceforge.net
[Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.] Jayz0999:
Good day mate, i have a redmi 9 (lancelot) all stock on miui 12.0 android 10 Q all stock.

Can you provide me a step-by-step guide on how to install this rom? Thank you.
[Xiaomi Poco X3 Pro] AiTakako:
in TRWP also i cant mount Data so i cant flash any SystemRW script.

i tried a script to flash and after that could change only permissions of folders or files, but dont open them (says is read only)

i used several explorers. Also any root apps trying changing build prop come up with a failure.

But i have root access.

i used the script from here Link but it came up with try manuallayy flash via TWRP...but TRWP cant mount Data...
[Xiaomi Poco X3 Pro] pl1992aw:
Flash the script via adb command under TWRP or use microSD card or USBOTG.
[Xiaomi Poco X3 Pro] AiTakako:
thx i tried but apsways say cant mount data
[Xiaomi Poco X3 Pro] samsungics1200:
you need to modify the flashable zip to be compatibe to android 12 and you may use a beta version of orangefox for data partition to be mounted and decrypted
[Android Q&A, Help & Troubleshooting] Erhy:
In my private webpage I want to show the SSID name, to know I am connected to my private WiFi Network?

Can I realize this, perhaps with a special android app?

Thank you for discussion

Erhy
[Google Pixel 6 Pro] nomisunrider:
You're not the only one...

https://www.reddit.com/r/GooglePixel/comments/wddk1s
[Google Pixel 6 Pro] jrg67:
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.

What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?

Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).
[Google Pixel 6 Pro] jrg67:
Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.

The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything.

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).

^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
[Google Pixel 6 Pro] Nergal di Cuthah:
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.
[Google Pixel 6 Pro] jrg67:
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.

How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?
[Google Pixel 6 Pro] roirraW "edor" ehT:
For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.

I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.

When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.

Your settings for the Android Flash Tool sound fine.

Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.

I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.
[Google Pixel 6 Pro] jrg67:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
[Google Pixel 6 Pro] roirraW "edor" ehT:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
[Google Pixel 6 Pro] jrg67:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
[Google Pixel 6 Pro] Lughnasadh:
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".
[Google Pixel 6 Pro] jrg67:
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that. 🙄
[Google Pixel 6 Pro] NippleSauce:
Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.

I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.

Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.

Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).
[Google Pixel 6 Pro] 96carboard:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
[Google Pixel 6 Pro] jrg67:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones. 🤦
[Google Pixel 6 Pro] 96carboard:
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.
[Google Pixel 6 Pro] jrg67:
Update:

Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.

1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.

2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far

3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.

4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.

5. Heating up during normal use - seems to be fixed

6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.

So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.
[Google Pixel 6 Pro] 96carboard:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
[Google Pixel 6 Pro] jrg67:
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.
[Google Pixel 6 Pro] minhgi:
Samsung Health took 23% of my battery after 3 days of monitoring and after A13 upgrade. You guys might want to check battery usage in setting. Deleted and battery usage return back to normal.
[Google Pixel 6 Pro] jrg67:
You are very right with Samsung Health app. I actually downgraded the app to the release from April and the phone is actually being let into deep sleep with battery being set to optimized and activity tracking on. When I had the newest version, I had to either disable activity tracking or put it on restricted battery for the phone to actually sleep. I left a review on the playstore about this and they replied to contact support. I haven't done that yet but you'd think they would be well aware of this by now.
[Google Pixel 6 Pro] minhgi:
Actually the latest Samsung Health work find on the A12 but you upgrade to A13, it cause a battery drain as soon as you activate with your account. It isn't going into deep sleep at all with A13.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Samsung always tells me the exact same thing every time I detail exactly what's wrong with any of Samsung's apps. I always feel like: surely, I'm not the only one, plus I go into great detail about what's wrong already. None of the times I've actually gone further directly with support about an issue has anything ever been resolved.
[Google Pixel 6 Pro] jrg67:
Yes I saw that as well but as I mentioned, either denying the app physical activity tracking or put the battery setting to restricted, it will help. Alternatively, you could do what I did and install the April version of the app and don't let the playstore update it. I got it from APKPure here https://m.apkpure.com/samsung-healt...th/download/6212007-APK?from=versions/version
[Google Pixel 6 Pro] minhgi:
Just found out my stock kernel and little cores don't idle either after a reboot.
[Google Pixel 6 Pro] Nergal di Cuthah:
Is assistant assigned to always listen? Iirc the little cores are for the AI (i mightvbe wrong though)

I think i'm wrong
[Google Pixel 6 Pro] kylechen:
Had similar problem with another phone.

My first step is, turn off all the network (mobile and wifi) for an hour, see the idle battery usage.

If battery turn good during "no network", it is usually app caused.

If the battery is still bad, there are issues deep down inside the system.
[Google Pixel 6 Pro] minhgi:
Yeah. I reinstall the A13 a second times on top of the existing firmware. That seem to have resolved the idle problem. Literally I never have to do much troubleshooting other than hiccups in the middle of the upgrade.

Thanks for everyone suggestion.
[Google Pixel 6 Pro] HipKat:
Battery drain and heat are a problem that's carried over from A12 for me. P7P can't get here soon enough
[Google Pixel 6 Pro] Aphex13:
Have any of you tried turning off your 5g? It seemed to fix most of my battery issues.

Type *#*#4636#*#* into your phone dialer.

Select "Phone Information"

Select "GSM/WCDMA/LTE (PRL)" under "Set preferred Network Type:"

*Be sure to take note of what is already selected here. It's "NR/LTE/GSM/WCDMA" on Google Fi.

This will prevent your phone from connecting to 5G.

To turn 5G back on, do the same, and select "NR/LTE/GSM/WCDMA" (or whatever it was before)
[Google Pixel 6 Pro] minhgi:
Hear alot of people have battery drain when 5G is enabled. I'm with Google Fi and on T-mobile network. That is very odd.
[Touch Cruise ROM Development] Bobby.pike:
Anyone got a link to the **OFFICIAL** o2 XDA orbit2 WM6.0 rom.

6.1 sucks

Thanks for help.
[Touch Cruise ROM Development] rspillo:
Look here, there are some original rom:

http://xdaforums.com/showthread.php?t=381600
[Touch Cruise ROM Development] rparslow:
UK or DE ?
[Touch Cruise ROM Development] Bobby.pike:
Uk

-The message you have entered is too short. Please lengthen your message to at least 10 characters.-
[Nothing Phone 1] SimMind28:
Is anyone else bothered by this? For a new company and new product you would think they would be up to date with firmware releases. Most other phones already have 13 or will get it this year, whereas we will have to wait maybe until June next year. Not impressed
[Nothing Phone 1] galaxys:
Bummer, but not surprised 😯📱🎲
[Nothing Phone 1] kalsuegtr:
It will better to focus on bug issues more than Android versions
[Nothing Phone 1] SimMind28:
Yup pretty pathetic that a new phone is already out of date lol. As long as Carl got Pei'd
[Nothing Phone 1] SimMind28:
Why not both?
[Nothing Phone 1] Sib64:
The Android 12 version of Nothing OS still needs work and stability.

It's not reasonable to switch to Android 13 until version 12 is completely reliable.

For info, the stable version of Android 13 has only been available for a few days, so please be patient ;)
[Nothing Phone 1] SimMind28:
Why couldn't they release the phone with stable firmware? Instead they release a glitchy phone and early adopters get to be beta testers except we dont get paid for it. At least Carl gets Pei'd
[Nothing Phone 1] aboutnothing:
Maybe nothing Paranoid android will come with android 13...

nothing is looking to recruit several android devs currently.

for android 13 let's let a few months pass for the majority of problems to be fixed on the vanilla version of android, for the moment there are still big issues
[Nothing Phone 1] SimMind28:
Why didn't they recruit a big enough team before releasing the phone so all the issues could have been fixed before the phone was released?
[Nothing Phone 1] AntoXik72:
What's the point? A few changes like icons ? We already have icon pack. I prefer having a bugless Android 12 than a full of bugs Android 13. Be patient, it requires work. If you're not, then do your own Rom based on Android 13 and share it with us. That's a one year company. It's already a miracle to sell a smartphone that fast. Being impatient isn't always a good thing man ;)
[Nothing Phone 1] SimMind28:
That's a flawed argument. Have you ever watched a movie and thought it was bad? You're not allowed to have an opinion on a movie unless you become a director and actor and release your own movie using that logic.

Sounds like a coping strategy tbh
[Nothing Phone 1] AntoXik72:
Maybe, but by choosing a phone from a brand new company, you can't except to have the same speed as company like samsung or xiaomi. Talking about them, when you see that they update to next versions but that they are full of issues, I prefer not to deal with those issues. If you wanted to always have the latest version before everyone, why didn't you choose a Pixel then? You have the Pixel 6A for the same price
[Nothing Phone 1] AntoXik72:
I'm not saying that Android 13 not before 2023 is a good new, the point is, if we have Android 13 in february but far more stable than in october with bugs everywhere, then I don't care considering the few changes between 12 and 13. On a day to day use, you won't even notice the difference
[Nothing Phone 1] rees54y:
Very disappointed, expected better . Might sell and buy something else
[Nothing Phone 1] Sib64:
You're reacting like someone who wants to have everything right away and above all without any problems, and that's just not how it works in the smartphone world, especially for a start-up.

I'm not defending Nothing in any way, but I must admit that this reaction makes me wonder.

That it's Samsung with an R&D office and huge resources that ends up with smartphones that have recurring bugs and critical problems too.

I think that now we expect too much from smartphone or electronics manufacturers.

There will never be 100% reliability, it's impossible!

Have you ever been part of a team that develops roms, applications?

If so, you should know that as soon as a problem is solved, another one arises, more or less important.

So you have to go through the whole command line to see the possible error.

All this represents time, money, and a lot.

I disagree with your comment that Nothing should have had a bigger dev team.

I think you were on OnePlus before, and also criticised OP for their dev teams!

You knew when you bought a Nothing(1) phone that you would have bugs for sure!

I remind you that it was the future buyers of the Nothing Phone(1) who put pressure on Nothing to release their smartphone quickly, but I can confirm that the communication model chosen (the Nothing Hype) is also a factor and has its negative side, and I got caught up in the hype too....

So yes, the Phone(1) is a smartphone with a number of bugs, but I think it's a smartphone that will soon be reliable.

So be patient and forgiving with Nothing.

Thanks and sorry if my comment may seem harsh, but I think that you will be ok with me (I hope;) )

Can I suggest you to read this news from xda about the Nothing timeline for Android 13 🧐

Nothing delivers updated timeline for Android 13
[Nothing Phone 1] Bec07:
I'm also very disappointed. 1.1.2 was already good enough. I find no deal Breaking bugs in ether 1.1.2 or 1.1.3. I wish they'd rather start developing android 13 directly instead of wasting time on software that is already ok enough.
[Nothing Phone 1] wolfaas12345:
Id say its a big DEPENDS if they polish the heck out of it iron out as many bugs and make it super smooth like 12 is on this phone id say its well worth the wait cuz no point in android 13 day one if its gonna lag crash etc like there's no tomorrow
[Nothing Phone 1] _c-:
Rom developers have a better chance of getting android 13 out for the nothing phone before nothing actually does 🤣
[Nothing Phone 1] lexcyn:
In the dev chat yesterday on Discord they said a beta would be released before the end of the year.
[Nothing Phone 1] _c-:
Still not a public release of android 13 for the nothing phone though. At this rate the phone is going to be behind. Other companies are already working on their version of android 13 which will be released way before nothing even starts working on android 13.
[Nothing Phone 1] Jbc00per:
Was it really a selling point anyways or implied that it would be out almost straight away. I'd rather them roll out stable updates and address things the community wants before jumping straight to 13. I'm enjoying using the phone so far and rather see new features first, Really don't see why it's such a deal breaker when even the S22 won't have 13 till towards the end of the year anyways