nazar-pc

Do I understand correctly that bypass charging is enabled automatically when charging limit is enabled?
It would make sense, though I expected a separate toggle or at least a mention of this on settings page.

secrec I'm typically not in favor of stop-charge limits, but the idea of not STARTING to charge until the battery level drops to a low threshold does make a lot of sense for some use cases.

I never bothered with any particular charging habits in the past either, its this phone that made me to.

secrec Question for you @nazar-pc ; you're replacing the batteries this often... where are you sourcing your replacement batteries? There are some really garbage quality battery makers out there, so if you didn't get a genuine OEM replacement, it wouldn't surprise me that the battery fails after a few weeks. You wouldn't believe the kind of thing I've seen with poor quality lithium batteries. Charged battery not even hooked up to anything just sitting on my desk for a few weeks and it puffs out.

The first battery was used genuine battery with probably less than 10 cycles, second time I purchased a battery replacement kit on iFixit, they partnered with Google and sell genuine parts (though it is $50 USD for a kit + shipping + forwarding to the country where I live from US, so it did cost me some).

spl4tt Google released "bypass charging" with the december feature drop. This would make charging absolutelly perfect.

Hm... I genuinely assumed that is how things always worked, but they only just implemented it 🤯

DeletedUser87 Possibly, it'd be great if I can configure that thing specifically: stop charging when let's say SoC reaches 90%, don't start charging until it drops below 80%. According to https://github.com/GrapheneOS/os-issue-tracker/issues/3213#issuecomment-2068161800 this is something that should be very doable.

AlphaElwedritsch Yes, you can, but currently not with GOS, as you have already established above.

I meant hardware features like camera. I acknowledge software side is different from stock.

DeletedUser87 It doesn't really make a lot of sense to me what you wrote. Battery is not charging constantly, it charges to 100% and stops there, that is exactly what BMS is there for, it will not "overcharge", we are not in 90s anymore.

Regular battery draining is hardly useful as well, it increases number of battery charge cycles, reducing its lifetime due to physical properties of the battery design.

The other frustrating thing is that battery was reported as "healthy" despite a few mm gap between the screen and phone body 🙈

I only had 23 charge/discharge cycles since last battery replacement due to keeping it on wireless charging most of the time.
Charging power wasn't high either, 3-3.5W only, even lower than typical 5V 1A wired charging.

What is concerning outside of that is that camera usage heats up the battery A LOT. For example I opened a camera app, started 4k video recording and in half an hour my battery was at over 46C. This time I made sure to not use a case, though most time I do.

Annoyingly, video calls in Telegram result in very similar temperature changes despite not recording video at anything close to 4k quality, it is probably 480p-720p. Not sure who is at fault there, but I suspect it is more likely hardware than the OS, but disappointing regardless.

I have replaced the swollen battery on my Pixel 7 Pro second time in less than a year yesterday.
It bulged and caused the screen to separate from the body.

Since this happened twice already and I'm not looking to replace the battery twice a year I contacted Google support about this and they recommended to limit SoC between 20% and 80%, but on Graphene OS there is no such option in contrast to stock OS.

According to Google documentation limiting charging to 80% can be done using "Battery > Charging optimization" (missing on Graphene OS). My pattern of usage actually seems to match somewhat what they describe in the documentation under "Protecting your battery" (also missing on Graphene OS) on the same page (I keep my phone on wireless charger 90% of the time and it SoC rarely drops below 90% and only a few times a year below 80% unless I'm traveling).

It'd be great if Graphene OS could adopt the same/equivalent features of the stock OS.

I saw https://discuss.grapheneos.org/d/9017-how-can-i-limit-battery-charge-to-80 and there is https://github.com/GrapheneOS/os-issue-tracker/issues/3213 that has priority "none" at the moment.

Just wanted to share the experience of this feature being not only theoretically useful, but also practically (assuming Google's documentation is to be believed). I believe having less flexible variant of this to start would be better than none at all, though I understand potential technical debt.

214b9821 I was also curious about webcam feature

matchboxbananasynergy

1. I am yet to see a banking app that works without Google Pay, certainly an option for someone who already has account in a specific bank that doesn't work without it
2. Only GrapheneOS developers can do that, users will have to at very least compile OS from source and wipe everything in the process of installation of custom version (probably some backend services will be necessary too), hard to call it an option
3. That would be ideal, but there should be some documented way how users can reach out to Google to add it, without active feedback certainly not going to happen

So no, contactless payments de-factor are not working fine on GrapheneOS. They technically could under other circumstances, but they most certainly do not today as far as regular users are concerned. We all understand that it is not GrapheneOS team to blame necessarily, but the issue clearly exists and is not solved.

My Pixel 7 Pro just rebooted itself in front of me. It is fully charged, locked and I don't have auto reboot enabled.
It was a soft reboot, started with Graphene OS logo right away.

This is the first time happened, but very concerning. I bought a new phone _a month ago.

Ciapp23 To be fair I think iOS wouldn't boot either if it was tampered with

Ciapp23 GrapheneOS will not even boot if it was tampered with. If OS is going to stay the same, the only thing that is going to change is data stored, which you can get rid of with factory reset.

So the question to you is what kind of problem you're expecting to fix with it? Because writing the same bytes on top of themselves is not going to change anything.

matchboxbananasynergy I was wondering why the issue was "closed" twice.
Very nice, hope new release works better!

discord You can install SSH server on GrapheneOS, but it is very much locked down anti-tinkering OS with strong focus on security, so you have much less things to tinker with.
It is also quite an expensive one at that. If you want to tinker with Aarch64 OS get SBC like Raspberry PI or one of numerous alternatives.

GrapheneOS uses very old version of SeedVault and is unlikely to get updated any time soon (see https://github.com/GrapheneOS/os-issue-tracker/issues/1924).
So yeah, backups are in a rough shape right now unfortunately.

dukhy-v-integrale I use AnySoftKeyboard (available in Google Play and F-Droid) happily for many years, but I don't know how it supports mentioned languages, but there are plugins for so many languages for it (installable separately) that it might just work for you.

I saw no issues using this keyboard with GrapheneOS.

unwat Well, if I were to reboot the phone, the process that was consuming CPU would have been gone too. But yeah, there appears to be something buggy about Wi-Fi debugging here.

The basics: opened shell with adb shell (Wi-Fi connection on GrapheneOS didn't work for some reason, I had to use cable), then top to find an application and top -H to get an idea of what threads in that application specifically, which might be useful hint for bug reporting.
Added details to this one: https://bugs.telegram.org/c/23348