Status Update
Comments
sp...@gmail.com <sp...@gmail.com> #2
I have forgotten to check the return value of open_output
in the "working" code. If I change wopenout
to
void wopenout (gzFile f) {
if (open_output ((FILE**)&(f), "wb"))
f = gzdopen(fileno((FILE*)f), "wb");
}
I get the same error as with the macro, so I suppose there is a real fd issue in this code.
ra...@google.com <ra...@google.com>
vi...@google.com <vi...@google.com> #3
There's another error in the test program as well, -Wall warns that gzFile fp is uninitialized. After fixing that it works again for the function implementation, but not the macro-implementation. So, this gives an error:
#include <zlib.h>
#include <stdio.h>
int open_output(FILE **f_ptr, char *mode) {
*f_ptr = fopen ("test.gz", mode);
return *f_ptr != NULL;
}
#define wopenout(f) (open_output ((FILE**)&(f), "wb") \
&& (f = gzdopen(fileno((FILE*)f), "wb")))
int main() {
gzFile fp = NULL;
wopenout(fp);
gzclose(fp);
}
and this works:
#include <zlib.h>
#include <stdio.h>
int open_output(FILE **f_ptr, char *mode) {
*f_ptr = fopen ("test.gz", mode);
return *f_ptr != NULL;
}
void wopenout (gzFile f) {
if (open_output ((FILE**)&(f), "wb"))
f = gzdopen(fileno((FILE*)f), "wb");
}
int main() {
gzFile fp = NULL;
wopenout(fp);
gzclose(fp);
}
and I cannot see why there should be a difference in behaviour. I also noticed that clang 11 gives a working program when using -O0, but -O1 or higher gives the fdsan error. clang 9 (which the ndk uses) gives the error for all optimization levels.
di...@gmail.com <di...@gmail.com> #4
Here's another minimal example, condensed from emacs, that fails:
#include <stdio.h>
int main()
{
fdopen (2, "w");
fclose (stderr);
}
My guess is that the sanitizer does not like that we do not use the fd fdopen returns when closing stream 2/stderr. If I change to this:
#include <stdio.h>
int main()
{
FILE *err = fdopen (2, "w");
fclose (err);
}
It compiles and runs without issues. Is there an actual problem in the first snippet?
th...@gmail.com <th...@gmail.com> #5
Is there an actual problem in the first snippet?
yes. you have two FILE*s that both think they own file descriptor 2. depending on what you're actually trying to do, you probably meant to use freopen(3) instead?
uw...@gmail.com <uw...@gmail.com> #6
Thanks for the feedback. The idea in the code is to open a line buffered copy of stderr, is that valid? I am still having some problems wrapping my head around the issue, so I would be greatful if you could have a look at the failing example below:
#include <stdlib.h>
#include <unistd.h>
/* If FD is not already open, arrange for it to be open with FLAGS. */
static void
force_open (int fd, int flags)
{
if (dup2 (fd, fd) < 0)
{
int n = open ("/dev/null", flags);
if (n < 0 || (fd != n && (dup2 (n, fd) < 0 || close (n) == 0 != 0)))
exit (EXIT_FAILURE);
}
}
/* A stream that is like stderr, except line buffered. It is NULL
during startup, or if line buffering is not in use. */
static FILE *buferr;
int
main()
{
/* Make sure stderr are open to something, so that the file
descriptor is not hijacked by later system calls. */
force_open (STDERR_FILENO, O_RDONLY);
/* Set buferr if possible on platforms defining _PC_PIPE_BUF, as
they support the notion of atomic writes to pipes. */
#ifdef _PC_PIPE_BUF
buferr = fdopen (STDERR_FILENO, "w");
if (buferr)
setvbuf (buferr, NULL, _IOLBF, 0);
#endif
int err = buferr && (fflush (buferr) != 0 || ferror (buferr));
if (err | (fclose (stderr) != 0))
return 1;
return 0;
}
Compiling and executing on device gives
fdsan: attempted to close file descriptor 2, expected to be unowned, actually owned by FILE* 0xaba9700c
Aborted
from the fclose (stderr) call, similar to in the previous very minimal example.
do...@gmail.com <do...@gmail.com> #7
The idea in the code is to open a line buffered copy of stderr
in that case you just want setlinebuf(stderr)
. see
ca...@gmail.com <ca...@gmail.com> #8
This is the same wireless charger the worked on Android 12 and would charge my phone in about an hour and a half.
This started occurring after I updated to Android 13.
ga...@gmail.com <ga...@gmail.com> #9
ma...@gmail.com <ma...@gmail.com> #10
ch...@gmail.com <ch...@gmail.com> #11
Thanks!
wc...@gmail.com <wc...@gmail.com> #12
di...@gmail.com <di...@gmail.com> #13
an...@gmail.com <an...@gmail.com> #14
st...@gmail.com <st...@gmail.com> #15
ch...@gmail.com <ch...@gmail.com> #16
rp...@gmail.com <rp...@gmail.com> #17
rk...@gmail.com <rk...@gmail.com> #18
rj...@gmail.com <rj...@gmail.com> #19
ph...@gmail.com <ph...@gmail.com> #20
ph...@gmail.com <ph...@gmail.com> #21
rj...@gmail.com <rj...@gmail.com> #22
da...@gmail.com <da...@gmail.com> #23
dl...@gmail.com <dl...@gmail.com> #24
ro...@gmail.com <ro...@gmail.com> #25
cc...@gmail.com <cc...@gmail.com> #26
Also filed
ti...@gmail.com <ti...@gmail.com> #27
hi...@gmail.com <hi...@gmail.com> #28
vw...@gmail.com <vw...@gmail.com> #29
Please provide an ETA for fixing this. If you have to take out the enhancement that might be causing the issue and put it back in later. But release a Quick patch and don't wait for Monthly updates.
re...@gmail.com <re...@gmail.com> #30
er...@gmail.com <er...@gmail.com> #31
ro...@gmail.com <ro...@gmail.com> #32
be...@gmail.com <be...@gmail.com> #33
fl...@gmail.com <fl...@gmail.com> #34
I really hope it doesn't take months to fix this...
ji...@gmail.com <ji...@gmail.com> #35
qu...@gmail.com <qu...@gmail.com> #36
an...@gmail.com <an...@gmail.com> #37
jr...@gmail.com <jr...@gmail.com> #38
ch...@gmail.com <ch...@gmail.com> #39
br...@gmail.com <br...@gmail.com> #40
ba...@gmail.com <ba...@gmail.com> #41
I contacted support, and after a lot of back and forth, the solution they offered was to extend my warranty and repair my phone.
They don't seem to understand that a physical repair won't fix the problem if the issue is with the new OS software.
They asked me for my IMEI number and checked whether I was eligible for such a warranty extension, which I was.
Here's the thing, it feels sketchy to me that they're offering that solution like they know specific devices were bricked after the OS upgrade, and just by replacing the bricked hardware with - a possibly newer - hardware, the issue may be fixed. It seems to me they know about this issue, but they're trying to hide it or minimize it or prevent class legal action against them... Or something like that.
Google, please acknowledge the issue and let us know you're working on it. If you really screwed it up and Android 13 did break the wireless charging capabilities of certain Pixel phones, also say that and let us know our options. Transparency here is crucial. I understand things like this can happen, but what's not ok is keeping your loyal users in a very annoying and upsetting situation without offering an explanation or proper support.
be...@gmail.com <be...@gmail.com> #42
lu...@gmail.com <lu...@gmail.com> #43
lo...@gmail.com <lo...@gmail.com> #44
ja...@gmail.com <ja...@gmail.com> #45
mw...@gmail.com <mw...@gmail.com> #46
ar...@gmail.com <ar...@gmail.com> #47
by clearing cache/storage on the pixel stand app, and then rebooting into safe mode. In safe mode the wireless charging worked again. Upon rebooting the phone . Wireless charging worked again. The android 13 upgrade messed up the pixel stand registration and completely broke wireless charging.
br...@gmail.com <br...@gmail.com> #48
This is interesting. I have noticed that my phone has started wirelessly charging again a few days ago. Nothing has changed, except for daily app updates and rebooting several times. I never cleared the cache on the Pixel Stand app or booted into safe mode. My phone seems to have "fixed" itself, although I am not so confident yet as to say it's now completely fixed. But I can say I have been wirelessly charging now for 3 days.
ke...@gmail.com <ke...@gmail.com> #49
fl...@gmail.com <fl...@gmail.com> #50
br...@gmail.com <br...@gmail.com> #51
ni...@gmail.com <ni...@gmail.com> #52
th...@gmail.com <th...@gmail.com> #53
ge...@gmail.com <ge...@gmail.com> #54
ma...@mattconnley.com <ma...@mattconnley.com> #55
da...@gmail.com <da...@gmail.com> #56
Clearing cache, safe mode, nor clearing cache on pixel stand has helped.
c....@newcastle.ac.uk <c....@newcastle.ac.uk> #57
da...@gmail.com <da...@gmail.com> #58
cw...@gmail.com <cw...@gmail.com> #59
tw...@gmail.com <tw...@gmail.com> #60
I thought it was the new v2 charger, but it doesn't matter what charger I put it on. It won't charge for very long before disconnecting, so I have to unplug my wireless charger each time and plug it into my phone.
rj...@gmail.com <rj...@gmail.com> #61
ni...@gmail.com <ni...@gmail.com> #62
September fix does not fix anything about wireless charging. Do I have to full reset my Pixel 4 after Android 13 update?
go...@stijnvandewater.nl <go...@stijnvandewater.nl> #63
Issue remains on my Pixel 4XL, even after the latest September update.
br...@gmail.com <br...@gmail.com> #64
Please note: After the Sept update my wireless charging stopped working again. Same symptoms as before. I then cleared the cache on the Pixel stand app, rebooted, and now wireless charging works again.
ni...@gmail.com <ni...@gmail.com> #65
br...@gmail.com <br...@gmail.com> #66
All I know is my Pixel 4XL is now finally wirelessly charging like it used to.
kh...@gmail.com <kh...@gmail.com> #67
pi...@gmail.com <pi...@gmail.com> #68
ch...@gmail.com <ch...@gmail.com> #69
go...@gmail.com <go...@gmail.com> #70
This is an overheating issue. You can get the phone to charge momentarily by putting it in front of the air conditioner, but then it will overheat again after 5 minutes of charging and stop.
ni...@gmail.com <ni...@gmail.com> #71
Pixel 4 updated to Android 13. Factory reset does not restore wireless charging.
re...@gmail.com <re...@gmail.com> #72
vi...@google.com <vi...@google.com>
bl...@gmail.com <bl...@gmail.com> #73
jo...@tegiffel.com <jo...@tegiffel.com> #74
Booted normal mode, and successfully charged wirelessly
ba...@gmail.com <ba...@gmail.com> #75
au...@gmail.com <au...@gmail.com> #76
cw...@gmail.com <cw...@gmail.com> #77
mode and charging works.
On Sun, Sep 18, 2022 at 2:01 AM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #78
ge...@gmail.com <ge...@gmail.com> #79
ni...@gmail.com <ni...@gmail.com> #80
Finally it works!
I followed those steps:
1) reboot in safe mode
2) wireless charging in safe mode (until it charges)
3) reboot
4) wireless charge, working!
cw...@gmail.com <cw...@gmail.com> #81
ba...@gmail.com <ba...@gmail.com> #82
cw...@gmail.com <cw...@gmail.com> #83
ni...@gmail.com <ni...@gmail.com> #84
I am sorry. The procedure I used does not fix the problem. It works for 2 days and after fails again.
bo...@gmail.com <bo...@gmail.com> #85
Google, why no response to your own issue tracking system?
cw...@gmail.com <cw...@gmail.com> #86
ni...@gmail.com <ni...@gmail.com> #87
Great job! Does Google decide to brick old phones to force to buy new ones? Well, I was thinking to upgrade to pixel 7. I think I will roll back to Samsung!
Have luck! Bye
ni...@gmail.com <ni...@gmail.com> #88
I guess the update to Android 13 compromised the hardware of wireless charging, impairing the functionality on the release (August) and slightly killing it on September and October update. I need Google let me roll back to Android 12 to check my hypothesis otherwise it must recall my Pixel 4 and give me another phone!
sl...@gmail.com <sl...@gmail.com> #89
bo...@gmail.com <bo...@gmail.com> #90
This absence of response to this and several other issues for months at a time or never at all sadly mean this will be my last Google phone.
ni...@gmail.com <ni...@gmail.com> #91
ge...@gmail.com <ge...@gmail.com> #92
cw...@gmail.com <cw...@gmail.com> #93
br...@gmail.com <br...@gmail.com> #94
tu...@google.com <tu...@google.com>
br...@gmail.com <br...@gmail.com> #95
nb...@gmail.com <nb...@gmail.com> #96
ca...@google.com <ca...@google.com>
cw...@gmail.com <cw...@gmail.com> #97
th...@googlemail.com <th...@googlemail.com> #98
jo...@gmail.com <jo...@gmail.com> #99
tz...@gmail.com <tz...@gmail.com> #100
Installed December update, all wireless charging ceased functioning. Does not even see a charger.
Only change was installing the update.
mi...@gmail.com <mi...@gmail.com> #101
wr...@gmail.com <wr...@gmail.com> #102
ep...@gmail.com <ep...@gmail.com> #103
jo...@oxfordschools.org <jo...@oxfordschools.org> #104
sa...@gmail.com <sa...@gmail.com> #105
29...@gmail.com <29...@gmail.com> #106
mi...@gmail.com <mi...@gmail.com> #107
ab...@gmail.com <ab...@gmail.com> #108
fo...@gmail.com <fo...@gmail.com> #109
I had a Pixel 7 pro, which wireless charging was working and stopped a few days after. Sent the phone back to google for reparation and they send me back another one.
THE WIRELESS CHARGING WORKED HALF DAY AND STOPPED ON THE NEW PHONE, the phone is not detecting any of my wireless chargers, this is insane....
Come'on, how can a feature like this could be brake for months with no real fix...
br...@gmail.com <br...@gmail.com> #110
fo...@gmail.com <fo...@gmail.com> #111
So I sent the second phone for replacement too... For now, it spent more time in google facilities than in my pocket.
So to sum up :
* The first phone, the wireless charging worked for 2 weeks
* The second phone works half a day
So let's go for the third phone (didn't received yet) and see what's next.
Did anyone get any answer from google ?
fo...@gmail.com <fo...@gmail.com> #112
br...@gmail.com <br...@gmail.com> #113
29...@gmail.com <29...@gmail.com> #114
At this point with people's warranties expiring this is malpractice on Google's part.
ka...@gmail.com <ka...@gmail.com> #115
pa...@gmail.com <pa...@gmail.com> #116
Guess Google is Apple's special lady and now makes Apple things work...
em...@gmail.com <em...@gmail.com> #117
ma...@gmail.com <ma...@gmail.com> #118
br...@gmail.com <br...@gmail.com> #119
mi...@gmail.com <mi...@gmail.com> #120
Im currently running `TQ1A.230205.002` and here are my steps:
- Settings > System > Multiple Users
- Turn on "Allow multiple users"
- Switch to guest user ("Add guest")
- Switch back to main user
Charging has been perfect since. I am not game enough to turn off the "Multiple users" setting yet, but have restarted my device and all working as expected.
br...@gmail.com <br...@gmail.com> #121
br...@gmail.com <br...@gmail.com> #122
29...@gmail.com <29...@gmail.com> #123
It is getting clearer by the day that they bricked our phones with zero intention to fix or compensate us for their own screw up. Total malpractice by google.
cw...@gmail.com <cw...@gmail.com> #124
shit at all. Mine is charging at the moment I can't trust it at all. The
fact that they completely are ignoring this is awful.
On Thu, Mar 23, 2023 at 9:31 AM <buganizer-system@google.com> wrote:
se...@gmail.com <se...@gmail.com> #125
st...@gmail.com <st...@gmail.com> #126
vi...@gmail.com <vi...@gmail.com> #127
st...@gmail.com <st...@gmail.com> #128
j....@gmail.com <j....@gmail.com> #129
Android 13
Build Number TQ2A.230505.002
Same issue here, pretty annoying.
st...@gmail.com <st...@gmail.com> #130
Android 13
Build TQA.230605.010
Will not wireless charge (started on last Verizon update actually) and Battery share can not be enabled at all.
cl...@gmail.com <cl...@gmail.com> #131
Android 13
Build TP1A.221005.002.B2
This is my 2nd time experiencing this issue. First time was probably a year ago. Lasted for about a week until I discovered the hack with the Pixel Stand app (multiple iterations of: force stop the app, clear the cache for the app, disable the app, reboot the phone). Following fix, phone has worked without issue for the last year. I charge primarily with wireless.
Issue reappeared this week. Noticed that it would show a charging icon, but battery was being depleted. Battery indicates "connected - not charging". Switched between Anker stand, Ioti car charger, and Pixel Stand with same results (all of these worked for this phone last week and all still work on Pixel 3XL and iPhone XR). Tried the same hack with Pixel Stand app with success lasting a few seconds and then reverting back to "connected - not charging".
Please advise on how I can help.
co...@gmail.com <co...@gmail.com> #132
Android 13
TQ3A.230705.001
Just started doing this today. So far, none of the troubleshooting or suggested fixes have worked.
Phone recently got the July 2023 update.
ee...@gmail.com <ee...@gmail.com> #133
Pixel 6 Pro
Android 13
TQ3A.230705.001.A1
Unbelievable this is still ongoing.
aa...@gmail.com <aa...@gmail.com> #134
br...@gmail.com <br...@gmail.com> #135
ew...@gmail.com <ew...@gmail.com> #136
Android 13
TQ3A.230705.001
Wireless charging stopped working randomly two days ago.
bl...@gmail.com <bl...@gmail.com> #137
Android 13
Wireless charging broke after the August 5th, 2023 update.
- Hardware: Tested on 4 different wireless chargers. swapped out USB3 cables that all charge the phone when plugged in. None wirelessly charged
- Safe Mode : worked momentarily in Safe Mode.
- Factory reset: Does not work in any mode after completing a Factory reset
- Android 14 Beta Upgrade: Opted into the 14 beta program and upgraded to 14 beta 5.2. Wireless charging still completely not functional in
lo...@gmail.com <lo...@gmail.com> #138
android 13
pixel stand 2 ($80) does not wirelessly charge and is completely useless. seems like it is a software issue not hardware. google will not give me a refund for it. it worked for a long time and then randomly stopped working. tried all suggestions. even replaced the charger itself.
vi...@gmail.com <vi...@gmail.com> #139
vv...@gmail.com <vv...@gmail.com> #140
Wireless charging stopped working.
Thought it's me doing something stupid. Replaced charger.
Actually, it's Google, acting irresponsibly.
pe...@gmail.com <pe...@gmail.com> #141
ge...@gmail.com <ge...@gmail.com> #142
And this was because just at the moment of buying, I heard a customer complaining about this exact issue.
The salesperson did their best to make the issue look like a faulty Pixel Stand, while they tried on-site to charge the customer device with a brand new Pixel Stand which was "oh what a coincidence!", also faulty? Bull****
ri...@gmail.com <ri...@gmail.com> #143
na...@gmail.com <na...@gmail.com> #144
li...@gmail.com <li...@gmail.com> #145
ti...@gmail.com <ti...@gmail.com> #146
First, "connected, but not charging". Went back and forth with Google support, they insisted it was a charger issue (it wasn't). Suggested I factory rest the phone (dubious)
Installed the latest update (Android 15) and had success for one charge up to about 85%. Then another issue.
Second, charging started to cycle on and off (every second or two) when connected to the wireless charger.
Tried just about everything: restart (no good), charge in safe mode (no good), charge in repair mode (no good), charge when turned off (worked once, then no good).
Haven't tried the factory reset as it doesn't seem to do anything based on all the fixes above, but might be a last resort. Checked the temperature using an app (no apparent issues) and even cooled the phone down in the fridge. Still no good after the first success.
Looks like this issue has been going on for over 2 years. No fixes advised in this forum which is laughable. Poor form, Google!
tu...@gmail.com <tu...@gmail.com> #147
this is still an issue. Google, can you please take your head out of your ... and do something, please?
Have Pro7, tried multiple chargers (QI cert. or not) and red numerous articles all over. Nothing worked (restart, turn off adaptive what-ever-s, safe mode... angry mode ... sad mode... ).
Please, Google, let us know it there is any light at the end of the tunnel, apart from schitching to other brands...
Thanks,
J.
Description
I just updated my Pixel 4XL to Android 13 two days ago and since I have not been able to wirelessly charge my phone. I notice it is much harder to align the phone to activate the charging, and even when I activate it, it does not charge.
I have never had an issue on Android 12 or any other version. Nothing has changed on my phone (apps, settings, hardware, etc), the only change was the update to Android 13.