Howdy folks, I've been running this a few days and here are my observations:
1) Touch input is very poor on the outer screen. It feels like I have water drops on it and the digitizer is confused. Might be some sort of sensitivity setting.
2) Complete loss of partially-opened functionality. Cannot open to use as a tripod to see the outer screen. The moment you open the phone even a millimeter, the outer screen shuts off entirely. Stock behavior is to use accelerometer and hinge position logic to achieve this functionality.
3) Pleased to see that WearOS now installs without the whole song and dance of side-loading the Chinese WoS app. Also Pixel Watch/WoS3 works fine as well. Google profile is properly copied to watches.
Pixel fold issues
2 months later
Hi,
I have the same issue with the outer screen turning off as soon as I open the Fold. I do not have any problem with touch on the outer screen though. Everything else seems to work great.
Just updated to Android 14 and have a question about Interpreter Mode for Google Translate:
It works beautifully for both languages on the inner screen, but does not display my translations on the outer screen for the other person to read.
I read on Google's support page that you have to use Google Assistant to enable Interpreter Mode, but I disabled the Assistant. Is there any way to turn it on in Settings manually? They mention a Translate heading under System in Settings but I do not have that option.
Is this related to the outer screen turning off when I open the Fold? Anyone else have this issue?
Thanks.
2 months later
Anyone else have their fold performance drop to nearly galaxy s7 levels? Seems like it's always battling heat and throttling when compared to my P6P on GoS.
4 days later
Are you still experiencing the performance issue?
a month later
bmisc all day every day. My Fold is basically unusable. Always warm, closing/restarting apps just swiping between two. It's like my phone has no RAM, and the CPU is on its knees.
I downloaded a resource monitor app a few months ago to see if my phone was pegged out somehow and it wasn't. It's just like something is critically wrong with the OS or the hardware. I didn't have this issue on stock, but I haven't tried it again since.
Thinking maybe there was a bug or glitch at some point and the updates are just piling on. I'll have to factory reset eventually. My pixel 6 pro running GoS is way way WAY faster than my Fold.
a month later
Even after a full rebuild of my Fold, I still commonly experience apps restarting. Just swiping from one tab to another in Brave, or from Brave to Proton Pass and back, the page will reload. It's almost as though my Fold has 64MB of RAM
14 days later
- Edited
Hello,
I have two issues that can be reproduced on two Google Pixel Fold devices (and which are not issues on Google Pixel 7 Pro), so they are Pixel Fold specific:
I cannot switch on my KeepGo eSIM (even though "eSIM support" is enabled). I tried to disable and enable it again and restart the phone multiple times, but nothing worked (with my Google Pixel 7, it works perfectly). See eSIM support
Google Maps, Bolt, and Uber cannot read their location despite having all necessary "Location" Permissions. What is interesting is that the GPS test works. See GPT test. I tried to change "Secure User Plane Location (SUPL)" and "Predicted Satellite Data Service (PSDS)" from "GraphenOS proxy" to "Standard" or "None", but it didn't help. I have the absolute same settings on these GrapheneOS on these two Pixel Fold devices, like on my Pixel 7 Pro, where everything works.
Any ideas on how to fix these problems?
The last problem is that the recent version DJI mini-application (for drones) doesn't work on all GrapheneOS devices
https://www.dji.com/mini-3-pro/downloads
I also tried to enable "Exploit protection compatibility mode" - it didn't help.
I cannot switch on my KeepGo eSIM (even though "eSIM support" is enabled). I tried to disable and enable it again and restart the phone multiple times, but nothing worked (with my Google Pixel 7, it works perfectly). See eSIM support
Reset cellular settings and try activating it again from scratch.
Google Maps, Bolt, and Uber cannot read their location despite having all necessary "Location" Permissions.
It sounds like you disabled location request rerouting for sandboxed Google Play without taking the steps required to have the Google Play location service working. Turn location rerouting back on in Settings > Apps > Sandboxed Google Play. The purpose of disabling rerouting is to use the Google Play location service, which requires giving it background Location access at a minimum but that wouldn't accomplish anything by itself. Our location rerouting provides an implementation of it not requiring granting the Location permission to Google Play services. The only reason you would need to disable rerouting and grant the Location permission to it would be to use their network location service, which would also involve toggling that on their Network location accuracy toggle. If you wanted to use that, you'd probably also want to grant it the Nearby Devices permission and enable the Wi-Fi and Bluetooth scanning toggles in the OS to allow apps you've granting Location / Nearby Devices to scan in the background when you aren't using Wi-Fi / Bluetooth. None of that is needed to use apps using Play location. Simply leave it as the defaults with Location rerouting enabled and Location not granted to Play services, which works fine.
I tried to change "Secure User Plane Location (SUPL)" and "Predicted Satellite Data Service (PSDS)" from "GraphenOS proxy" to "Standard" or "None", but it didn't help
You should change these back to GrapheneOS. It's definitely not related to those settings.
- Edited
The last problem is that the recent version DJI mini-application (for drones) doesn't work on all GrapheneOS devices
This is a bug in the app which is using a private ART API causing it to break in AOSP 14 QPR2. We've worked around it and the issue is resolved for them in the upcoming GrapheneOS release today. It's an app bug though, and they may end up needing to fix it themselves. It doesn't occur with the stock Pixel OS because it uses an older version of the Android Runtime from the March mainline module release which is still essentially Android 14 QPR1 with additional fixes applied so it doesn't have this change breaking these apps yet.
GrapheneOS thanks a lot!
The location thing seems to be solved!
Does "reset cellular settings" mean I must delete the existing eSIM and add the new one? I don't see any other option (I cannot enable this eSIM at all to do any settings)
Because in that case, I have to buy a new one.
a month later
I've rebuilt my Fold a half dozen times since I bought it and installed GoS. Within days each time I start experiencing apps that close just from swiping away to any other app. Example, snagging a password from a manager and going back to browser. Anything like that.
Is this a limitation of the Fold itself, or just that there are quirks with GoS running on the hardware? There are times during the day where I get so pissed that I pull out my Pixel 6 Pro with GoS and it runs circles around the Fold, running the same exact suite of apps.
Anything I can do to troubleshoot these annoyances?
My system is taking up 330GB. I bet that's why I'm having issues, at least right now. I don't even know how that's possible.
Could be a hardware issue, but I don't know why it would cause the system size to be 330GB.
I decided to completely wipe, and actually re-install the OS from USB.. the last two times, I just did a factory reset. Perhaps something became legit corrupt with the OS in the last 9-10 months, and it was carrying forward despite resets.
- Edited
scrampker Could be a hardware issue... What is the total storage available in your Fold? Is it reporting more space used than you have available?
/system is read-only, so can't really clean it up or reduce space, but @GrapheneOS may figure it out for ya!
Maybe don't restore a backup after wipe.. I rely in backups myself so I know how painfully that is, I have lost USB sticks with backups too! I empathize... However the issue may me carried forward in backups so its worth a try!
Also resettling network settings shouldn't delete your eSIM, I've done it before and my eSIM was OK afterwards!
scrampker 330GB! That's crazy. My Pixel Fold's System reports using 14 Gb, so something somewhere is misconfigured.
No, this information is wrong. System isn't the size of the OS. System is the size of data not included in the other categories. System includes user data that's not part of the other categories. The size of the reserved SSD space, OS and firmware are a fixed size included in the value which do not vary across devices and the rest is data stored by the OS in the data partition. The firmware/OS partitions cannot be larger on one person's device, it simply isn't how it works. People are misinterpreting what System storage space means.
After a few days, and all apps re-installed (but not all configured yet,) I'm at 86GB system and 81GB apps. I realize that the phones are categorizing the storage weirdly, and it's not to blame GrapheneOS for this. I was merely pointing out how crazy high it was, for no apparent reason. Sorting apps by storage use proved fruitless. No idea what happened.
That being said, I do have a 512GB model, and my phone is slow as dog crap again with my apps installed. It's very common to swipe from an app to my password vault, to find the vault app has restarted itself, select the username, and swipe right back to the previous app, for it to have restarted as well. Sometimes I get really lucky and I'm able to keep both apps active by swiping back and forth quickly multiple times, but that's about a 50/50 chance. Really not sure why.
I have a 1-for-1 app load on my Pixel 6 Pro, also running GrapheneOS (of course,) and it leads me to believe that either the Pixel Fold just sucks in comparison, or there's some little niggle in the GoS implementation on the Fold. I'm honestly clueless and not attacking the Graphene team at all. Other than the slow performance, commonly warm hardware, and experiences listed above, I've always enjoyed this operating system on 4+ devices.
I really doubt it's hardware. I just think the initial reports about the homegrown silicon are likely very true, and this just cannot compete with the Qualcomm in the Pixel 6 Pro. :Shrug:
scrampker The Pixel 7 Pro has the exact same SoC as the Pixel Fold, they both have the Tensor G2, and they both have 12GB of RAM. The Pixel 6 Pro also shares 12GB RAM with the other two above devices, and carries an original Tensor SoC, which is very similar to the Tensor G2. .
It only differs in that the mid cores were upgraded to a slightly more modern (but not completely modern) core by changing out the 2 Arm Cortex-A76 cores for Cortex-A78 cores. The rest of the chip remained the same.
Both chips were known for heating up quickly, and when I had my Pixel 7 Pro I ran it rooted with a locked bootloader and verified boot for months. I ran a kernel manager that allowed me to examine and adjust the governors and clock speeds on the different cores, but I couldn't override the thermal throttling. As soon as the prime cores (2X Cortex-X1) powered up to max, they only could hold that speed for less than 10 seconds before the whole chip, all three sets of cores throttled down! They were programmed with the default SchedPixel govenor, a custom one Google made, to almost never go up to their full speed however. They usually would boost up when system was under heavy load, like >70% for periods of <2-3 seconds then go back down to 500mhz to rest. Only when doing really heavy loads did they get going and that resulted in the whole chip throttling!
Really I'm not surprised that both your devices, having those SoC's, your having issues. However the issue with your apps closing so fast in the background is a new one to me... It sounds like in Developer Options, "Suspend execution for cached apps" may be enabled, but I'm not sure. Maybe try setting this to disabled?
I think you need to swipe your notification screen down twice, to get to quick settings and in the right bottom part it will show you how many apps are active in the background. My Pixel 8 Pro runs great at between 4 and 8 even at a time. No problems like you are reporting at all! My zRAM is mostly full but I always have around 2GB of RAM free, and yours should as well unless you have a lot of apps in the background and running! Check that place in the quick settings screen, and when you click on the number you get a screen where you cab stop those apps too.
Be glad you didn't geyvan 8GB model like a regular Pixel, I don't think those would deal with backgrounding apps well...