Android 13 for Pixel #Blog
This post is seeing the light of day once LineageOS promoted the device to the Android 13 build roster. And yeah, on September 7, this is finally a thing.

For a long time, the development has pretty much paused over at Android 11 as Android 12 has some harsh requirements which the Pixel 1 didn't fulfill by default. Some developers tried their best to build it but still ended up with a non-bootable build. After that, everything was just left aside, with Android 11 ROMs continuing to receive security patches update.

One day out of the blue, a XDA thread surfaced. Everything is normal at first, LineageOS 20, Android 13, unofficial build, Google Pixel... wait, XL? No number at the front? That means it's for the first generation Pixel, unbelievable. It's kind of a shame when older devices could boot the latest Android version while ours are just stuck at Android 11, but well, I guess the title is finally coming to an end.

One such build inspired a few developers to start putting effort to the device tree. Nolen Johnson is the LineageOS maintainer for the first generation Pixel as we have all known of, since the debut of the Android 13 build, he changed his mind to revive the development for the device again, but not until a few months later, the hard work has finally paid off.

Yup, Pixel 1 devices can finally enjoy Android 13 LineageOS weekly build before Android 14 is released. Anyway, it's so nice to see it becoming a truth in front of us. Hopefully it could continue receiving support till at least the Pixel 10 is released, finger cross. Of course, the longer, the better.

#LineageOS #Official #A13 #ROM #Sailfish
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel (sailfish)
Updated: 12/9/2023

▪️Download [728MB]
▪️XDA

Changelog:
• Fixed Wi-Fi panic issue

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #ROM #Marlin
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel XL (marlin)
Updated: 13/9/2023

▪️Download [733MB]
▪️XDA

Changelog:
• Initial LineageOS 20 official build
• Aperture:
- New camera mode selector UI
- Cleanup cameras parsing
- Properly observe / remove observers from LiveDatas
- Use Material You colors on QR bottom sheet
- Use Material You color on location dialog
• AOSP Keyboard:
- Add number row option
- Implement space bar cursor trackpad
- Material You styling updates
- Make long-press key hints configurable
- Add option to always show the emoji key
- Set navigation bar color to KB background
• Source Changelog

Notes:
• How to flash guide
• Upgrading from 18.1 official guide
• Repartition required
• MindTheGapps is the only supported GApps package (AFH | Mirror)
• Unofficial build by @npjohnson with Google Apps/Pixel goodies included. OTA's roll roughly once a month. (We won't be posting it over here.)

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #Archive #Sailfish #Marlin
📁 LineageOS 20.0 First Official Build Archive for Pixel & Pixel XL
I can't be sure but is this the first device supported by LineageOS to get promote by skipping over one version release? At least it is one of the few ones.

Anyway, welcome to the LineageOS 20 club. We actually managed to experience the latest Android version for a slight moment again. Just another first build archive to record down the momentous day for the Pixel 1 community.

Good things must come to an end, so seems like our Pixel 1 ain't a good thing huh (UFS, microphone, camera...). Going forward there will be weekly update for these two devices, so the channel will be back to normal operation once again.

Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #ROM #Sailfish
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel (sailfish)
Updated: 16/9/2023

▪️Download [728MB]
▪️Repartition
▪️XDA

Changelog:
• Updated translations
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

The Wasted 8 KiB Space #Blog
Sorry, I know it's kind of dumb but I have to come up with this post. Yeah, 8 KiB never seems to be a big deal for people these days, like the space is just too negligible at this point, but well, why waste it when you could just use it? Yeah, I expected people to come out to say, what can you fit with 8 KiB. What's so important about it?

Just change this perspective to real life, usually when you want to rent a space (to sell things), you are required to pay according to the area size you are going to use, which is basically buying phones according to their storage size. So now you have rented the space, and of course you want to make use of every single inch.

Assuming you did your research carefully and bought a display rack that will fit nicely at one corner, but then just realised you couldn't put it the way you want because something else is obstructing (like water leakage or something). You are then forced to move the rack out a little and then too bad, it's blocking a quarter of the corridor width.

So yeah, not a big deal, right? Some people who have walked through that specific corridor will already be leaving a negative impression because it's so inconvenient, and so how does this relate to phone's storage? 8 KiB equivalent to blocking a quarter of the corridor, how does this make much sense? In a space, we have many corridors, and that's just one corridor being narrow, not a big problem, right?

Obviously, this was never a direct convertible thing, we have no corridors or customers in the phone's storage space world. I know, hardly any files we stored are even in this minuscule size these days, what's the deal here? Since you paid for it, then you should be able to use it. Like you bought multiple packs of paper and it said there are 50 sheets in one pack, and you just realised some of the paper packs are short by one sheet, do you leave it as it is or what?

This is kind of going off topic but I wanted people to know that since you use your money to buy your phone, then you should make use of the thing in it. I know 8 KiB is never going to make people die, suffer or whatever, but I just want this to be open and transparent for people to know that they have lost something ever so slightly. Next time let's just waste 8MB instead, it won't make any difference too.

If you didn't know what I was referring to, recently both 2016 Pixel models received LineageOS 20 support, and in order to flash, you will need to repartition your device to get it work. The repartition script that is available for the 32GB models has wasted 8 KiB worth of space, but if you really care about it, just get the revised version from here, it's the same thing but just retrieving back the 8 KiB space. After all, the choice is really up to you over here.

#LineageOS #Official #A13 #ROM #Marlin
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel XL (marlin)
Updated: 20/9/2023

▪️Download [733MB]
▪️Repartition
▪️XDA

Changelog:
• Updated translations
• Update Chromium Webview to 117.0.5938.60
• September 2023 Security Patch
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #ROM #Sailfish
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel (sailfish)
Updated: 23/9/2023

▪️Download [729MB]
▪️Repartition
▪️XDA

Changelog:
• Update Chromium Webview to 117.0.5938.60
• September 2023 Security Patch
• Dialer: Fix in-call vibrations
• Calendar: Updated to version 1.0.36 (Etar)
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

Failure of Helping #Blog
I am doubting whether to release this post or not as it was a second part of last week's post, and it seems like the early reaction gave a yes to it, so here you go. And good luck to those 32GB Pixel users who needed repartition, I really tried my best to help you guys, but that's all I could do.

From the early days, we are taught to be helpful people. Some people tried their best, but sometimes reality is cruel, not all attempts are going to be a success. You know, there are some people who just don't like getting interfered with by others, they just prefer their own ways.

Yeah, we know that official things are trustworthy, and in case you have any problems with the products, the respective company can respond back. Nothing can be perfect, so some people try to modify it and recreate a better version, but then the original company will just consider it as a "counterfeit" product. It's normal, since those changes aren't under their control and they don't know what has happened under the hood.

You wondered how this is related to your Pixel 1? Nothing related to the device itself, but the community. With the Android 13 arrival, repartition is now a thing that we have to do if we wanted to use that. If you ever requested help on the partition thing, chances are you will be asked on which version of the script you used. For the repartition script thing, technically anyone could check what changes was being made there, everything is open and transparent here, and I will confirm it one more time: it's the same thing as the original one, but better, you know.

I will just straight up say one thing, a second or revised version of the script will never exist if the issue was fixed. The existence of the script is for the better, at least for the 32GB models. If you are really curious about what's inside the script itself, download and check the file inside. Here's a brief summary on what was added and changed in the revised script:
1. (Irrelevant error) "Repartioning". → "Repartitioning"
2. (Safety measure) Check if device is sailfish or marlin
3. (Status) Displaying status/progress of the repartition
4. (32GB specific) Retrieving back 8 KiB worth of space

No choice, an official statement will be issued and saying that "it is not the same thing, only use the one that is provided from us," in case you wanted support from them. What's my stand of view over here then? 128GB users, you are good to go, just use the one from them; 32GB wise, get the revised version. I mean, sure, if the repartition script for 32GB got the issue fixed, I am willing to remove the revised version, but you know, that's not going to happen.

#LineageOS #Official #A13 #ROM #Marlin
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel XL (marlin)
Updated: 27/9/2023

▪️Download [733MB]
▪️Repartition
▪️XDA

Changelog:
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #ROM #Sailfish
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel (sailfish)
Updated: 30/9/2023

▪️Download [729MB]
▪️Repartition
▪️XDA

Changelog:
• Fixed random fingerprint reboots
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

'Exaggerating' small issues #Blog
Just to get things explained well, this will be the sequel of last week's post. For those who don't care, no need to express the feeling, I just wanted to inform the users who are getting affected, this post isn't targeted at you, thanks for your understanding.

Anyway a small update on the repartition script before we get into the main topic. Apparently both repartition scripts have some minor errors, which means 128GB users are also affected but they are just losing a mere 4 KiB here. Both revised repartition scripts have been updated to resolve this issue. Yes, I understand this makes small to no difference, but I am purely here just to help people.

You guys probably didn't know this, but reporting small issues is what makes a person or thing improve over time. Whenever there are any issues, we improvise on it and make it correct. Oh yeah, I shouldn't have just written one dedicated post about wasting 8 KiB through a simple repartition script.

Okay fine, I admit the fact I exaggerated it, because I have explained why the revised version exists in the repartition guide post, so there's no need to repeat it over and over again, smart people make the best decision for themselves. I also did admit it was kind of dumb to write and then released it onto the channel.

Since we still have some space, I will just talk about the blog posts on this channel, you should know it's related to the Pixel devices or the community itself. At first, it was just about my opinions on my own device experience, then later with some additional community related posts and we came to a temporary pause.

The day when LineageOS officially supported the device with Android 13, it hyped up the community once again. In the installation guide, it mentioned about repartitioning the device. I am just curious what was inside the repartition scripts so I gave a look at both of them. It was this kind of dumb action that led to all this drama. Next time let's just make the script closed source to prevent such things from happening.

And whatever was the story, you know where to look for it. I really have no intention to hurt people unless you really want to dig your own grave for some weird reason. Just for your information I did not mention a single person regarding this case. I am purely here just to help, I did my part and the rest is on you, the user.

#MadeByGoogle
Everything you need to know about the Made by Google '23 event

Today, on October 4th Google is releasing the Pixel 8 and 8 Pro phones, the Pixel Watch 2 and more!

When? 10am Eastern Time (7am PT, 9am CT, 2pm GMT, 4pm CEST, 7:30pm IST, Oct 5th 1am JST)

Where? YouTube or Google Store (there are also live streams in ASL, German, Japanese and Spanish)

As always, we are going to cover everything about the event on Telegram and Twitter if you're not able to watch it ❤️

Follow @PixelHubUpdates

#LineageOS #Official #A13 #ROM #Marlin
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel XL (marlin)
Updated: 4/10/2023

▪️Download [733MB]
▪️Repartition
▪️XDA

Changelog:
• Fixed random fingerprint reboots
• Updated translations
• Update Chromium Webview to 117.0.5938.140
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

#LineageOS #Official #A13 #ROM #Sailfish
LineageOS 20.0 - OFFICIAL | Android 13 | Pixel (sailfish)
Updated: 7/10/2023

▪️Download [729MB]
▪️Repartition
▪️XDA

Changelog:
• Updated translations
• Update Chromium Webview to 117.0.5938.140
• Fixed camera, slow-mo, and night light issues
• Source Changelog

By @npjohnson, @electimon
Follow @Pixel1Updates
Join @Pixel1Chat

7 Years, What's Happening Next? #Blog
As time passed by, more and more people started to switch phones as the hardware couldn't catch up with the game. Some probably keep the old one to use as a backup device in case it is needed. Pixel 1 is still capable of being a communication tool and browsing the Internet. 4GB RAM is still pretty sufficient for such tasks on a phone, though it's already seven years old at the time of posting.

In order to have a functional phone, you need to have both hardware & software working together. You could see the hardware part as a human body, and then software as the system that is actively running inside the body for many years to come. So without the hardware, you couldn't run the software at all. For software wise, the good part about Android phones is that you can unlock the bootloader and flash something else if there is one being made.

So how does this relate to the Pixel you might ask? You probably heard of it somewhere before, but many Pixel 2 are actually facing camera issues that the owners have to use a magnet to fix it temporarily, some Pixel 1 also faced UFS issues which cause the device not to boot up at all. Yes, Pixel comes with good software out of the box, but the hardware that is sustaining the software to run isn't any good after all. I didn't mean that Google hasn't improved it in their recent models, time will tell whether the improvement is enough or not anyway.

For lucky Pixel 1 users, some are able to use it for much longer before that happens, or probably not having to face it at all, but it seems like the good luck never lasts. The hardware just started to fail itself over time, and it's understandable if others couldn't last, but the problem is they worked. So does that mean Google just put in some cheaper components which are only meant to last for a few years because they know the majority will have switched by the time they are about to fail?

In my humble opinion, phones should be able to last forever. I mean, one day, when all these become history, people in the future could still get to see them working in action. Some managed to take attentive care on some old hardware and when they revisited it, those just work like charms when it's being demonstrated.

As this is only going to happen for more in the future, eventually affecting both users & developers, the amount of people with a working Pixel is only going to decrease over time, which means this community is just going to be just dead. Well, some people don't mind getting some value from this channel but some wanted it to be just a pure Pixel 1 development only channel, obviously leaving it dead is going to be the best option.

I never publicly said this anywhere but this particular channel is going to be flexible in content around Google Pixel, from writing weekly reports till LineageOS till blogs, many things have happened. Many would have asked why not just create another channel for all those things? Basically blame Telegram as they limit the number of public groups & channels you can own, I have created more if there isn't such a limit or the limit is further away. Also I can't guarantee I would have the time to manage all these stuff.

What's next for this channel? Irregular blogs & memes (probably never) might pop right off over here, but well, not to worry as it's still Google related content. Still, as promised, if there is any development for the Pixel 1, we will post about it. It will continue to serve as a place for such things, but with additional contents here. Thanks for staying around!