D

dmadhatr

Unfortunately, this became a moot issue today when speaking to the cell repair company (only one shop here works on Pixels) - port / battery replacement was north of the cost of each individual Pixel 5a and 4a with 2.5 hours to solder for each - so they are just going to be replaced, he was not able to provide more input. Just eaier to buy another phone. Went ahead and ordered another updated Pixel, the Pixel 6 that got here today has Qi, so, USB charging doesn't matter as much - that works fine.

I will not be providing more input on this issue.

Appreicated.

The work phone is a 5a, not a 5 ( 5a still gets full updates), will retire the 4a if you guys are telling me it's insecure - will move the work SIM to the 6 - do you have a roadmap for when you will no longer fully suport that 5a?

Thank you @Carlos-Anso

For GrapheneOS, no, I've trusted your organization enough not to haved used the ADB SHELL on any of the two phones listed above. The boot loader was locked after initial install of Graphene OS as well per instructions. They are both stock and received regular updates (for the 4a it's on whatever pushes come from the extended support updates). I am very familiar with side commands in the ADB SHELL. Since I've not had an issue to debloat a GrapheneOS phone, I haven't resorted to pulling out software ever/yet.

Again, per creating a fair baseline - I'm unsure if any charging issue may have caused this issue for both phones in the same week - without knowing what logs to gather, I can't provide any additional information for troubleshooting. I won't continue to hyperfocus on the update as the cause since I would like to replace the ports and batteries in both first. The only logical baselines I can offer is to replace the traditional source of known hardware issues for these models of phones, the ports and batteries - and then use the pro-offered Google chargers for these models. One phone charged from a conditioned power supply, the other phone was on it's on standard USA 15 V 125 V outlet (line tested good for informational purposes and is properly wired per the check I did with a Klein Tools GFCI Receptacle Tester). The chargers were vendor provided, I do not know if they subbed any third party parts, just the chargers they came with from the retailer.

At this point, until I have better evidence, I will tenatively withdraw my assertation that it may have been an update. After reading through the comments provided by your group on this thread, it only makese sense to reduce known causations for this issue.

As stated, the only way I can know for certain is to replace the aforementioned parts, standardize the charging conditions and create a baseline that is fair for troubleshooting.

Additionally, the Pixel 6 (ordered and en route) will only charge from the provided charger/cable - if it occurs again on all three devices (the two going into the shop this coming week days), I would like to go further into this issue with the Graphene Forum to isolate causes.

Appreciate your response.

Fine and fair enough - it's your forum @other8026 and understood - not my community and I get it.

Here is the deal, I'll do this:

Both of the phones mentioned above will go to the shop, I'll have both USB-C connections replaced on those ports and the batteries. Already spoke to them previously this past week, and they are certified to work on Pixels. This will be done as a sanity check. This will give a good base line for eliminating factors that may be an issue.

Also, I just purchased the exact Pixel chargers and cables to eliminate that as an issue.

Plus, I just bought a Pixel 6 (not 6a) that should be here this week - I'll put Graphene on it, run it and let it update.

If the issue still occurs, I'll post a $1,000 bug bounty to fix this issue, OK? Alot of people are running into this problem, so it would be worth it to get it resolved.

Thanks for your time.

Also, if the person who posted above with a Pixel 7a is having the same issue, wouldn't it seem logicial to assume the issue isn't the hardware that's been acting normally and then suddenly caused an issue, but an update?

The point is, is this non-sense can be fixed by simply side loading an adb shell command, that would be great - if not, it's an issue that needs to be addressed.

I'd appreciate someone on this project with knowledge of this issue to offer some type of resolution, even if it is down the road.

Actually it does have Bixby in the screen window on volume up power on.

Stated, de0u, nothing you wrote contributed to fixing the issue, so not sure why you posted.

If I choose to use those two models of phones, its supported and that's my business.

I'm definately no longer financially donating to this project if this is normal type of response one will get - people are having issues caused by the code update, they can address it [removed]