[Beta] Pixel 2 installer config

flohack

@flashylinux Ok can you check after it bootloops if there is anything in /sys/fs/pstore?

FlashyLinux

@flohack

That folder is empty

FlashyLinux

@flohack

I cant edit posts I guess after so long so I am double posting but.

I have not been able to find any file in that directory.

Try #1
Steps

Wiped everything using TWRP
Flashed boot with “halium-boot_walleye.img”
Flashed dtbo with “dtbo.img”
Flashed vbmeta with “vbmeta.img” using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rebooted device
Let Boot loop 3 times
Booted into bootloader
One time booted into TWRP

Result – Directory empty

Try #2
Steps

Flashed boot with “twrp-3.3.0-0-walleye.img”
One time booted “halium-boot_walleye.img”

Result – Directory empty

I also noticed I was using boot slot "b" and changed it to "a" to see if that made a difference. DO NOT DO THIS. It would not allow me to boot or flash anything. It wouldn't even finish flashing a factory image. I changed it back to slot "b" and everything was back to normal.

RVan

Following...

agates

@Flohack This page at postmarketOS wiki states some issues with pstore. Is it possible we're facing the same issues?

https://wiki.postmarketos.org/wiki/Google_Pixel_2_XL_(google-taimen)

EDIT:
Also wondering if we need to set clk_ignore_unused=true, though I'm not sure how or if you've already configured that

flohack

@agates Ill take a look. Well idk how to set clk_ignore_unused but I will try to find out.

agates

@flohack Looks like clk_ignore_unused may be needed as a command line boot option, if I'm interpreting this correctly?

https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)

If there's an easy way I can test that I'd be happy to, though I realize the same chip is used in taimen and not having this issue.

flohack

Some small progress I have a Pixel 2 now in my hands and can reproduce the bootloop Probably going to attach a UART serial cable via USB to see whats going on

flohack

@agates Yes indeed adding clock ignore helped. Though now the problem is, will that keep some hardware out of sleep state, and impact battery life?

agates

@flohack Awesome! I guess it will be hard to judge battery life since I haven't used the thing as a daily driver for over a year. I'm eager to try it, though, at least to have a phone to develop apps against.

flohack

@agates you can try to run this installer config manually with ubports-installer -f walleye.yml - https://github.com/ubports/installer-configs/pull/150

agates

@flohack It's working! Typing from ubports on my pixel 2 now!

Thank you!

Keneda

@agates said in [Beta] Pixel 2 installer config:

@flohack It's working! Typing from ~~ubports~~ on my pixel 2 now!

Thank you!

Ubuntu Touch / uTouch

agates

@keneda said in [Beta] Pixel 2 installer config:

@agates said in [Beta] Pixel 2 installer config:

@flohack It's working! Typing from ~~ubports~~ on my pixel 2 now!

Thank you!

Ubuntu Touch / uTouch

Ahhh yes, the behavior that drove me away from the community all those years ago: people arguing about the names of things instead of making the experience better for developers

Keneda

@agates
Wow, how can someone feel so bad just because we tell him the right naming of things... ?
Ubports devs themselves remind sometime people here, that ubports is the association that maintain the OS, and not the OS itself , wich is uTouch.
Anyway, sorry hurting your feelings teaching something with kindness.

flohack

@agates Well to be honest, we are we very peacefully about slight variations of things, but with the name of the OS vs the name of the Foundation we need to be strict:

UBports Foundation is the organization doing development for, but not limited to...
Ubuntu Touch, which is the official name for the thing we are doing

Why is this important? Ubuntu Touch is containing the word Ubuntu, and its use is being licensed by Canonical Inc. to us so that we can carry on. We do not want to mix it with UBports, and btw @Keneda also uTouch is wrong and please do not use it :). Since if we get sloppy with that, Canonical might think we do not need the license anymore, and revoke it maybe.
Also we are entitled to sub-license the use of "Ubuntu Touch" to vendors and third parties that want to pre-install Ubuntu Touch on their devices. That is a specific right we can give or deny!

So, to stay clear of and issues with that, please stick to the naming. Also UBports should not be used as a name for 3rd party Github repos, and other project names, since it marks projects as "officially run by the foundation" in perception of the end user. And there we are strict, you cannot use our name for things that you are doing. You can use "Ubuntu Touch" however...

BR Florian

Keneda

@flohack
I know uTouch is far from being endorsed by Canonical (so you, as ubports, can't endorse it neither), but it's the "little name" lot of users use so i name it because he can see it here and there

Moem

@keneda said in [Beta] Pixel 2 installer config:

it's the "little name" lot of user use

To be honest, I've only ever seen you using it. And since you've been asked to not do that anymore, I assume we won't be seeing that again.

Keneda

@moem
Well if you search forum you'll see i'm not the only one doing that, even if sure i'm quite active here so lot of recent entries are from me.
It's been quite from the beginning of Ubuntu Touch that this "compressed" name was used (maybe because of some things like that, who knows...).

Now like you say, if using it make people here inconfortable i'll no longer use it with no problem.

agates

@Flohack thanks for the explanation.

I just thought this comment was unnecessary and out of context. I'm an outsider, don't particularly care (no offense, I detest arguments about labels), and if the project has naming issues perhaps it should be addressed with branding and not forum posts.

Regardless! This is a pixel 2 thread. You were right about the battery. It didn't even last 12 hours for me with just wifi on with nextcloud/caldav and dekko/imap sync.

The good thing is bluetooth etc works fine for audio so far and I was able to pull up a video to watch via jellyfin/jellyfUn. I had no visible issues on install as a user who doesn't know specifics to look for.

It's otherwise sluggish but bearable for a first build. Some of the battery is likely due to age and wear as well, I was pretty rough on this thing. Never been a fan of its USB-C port anyway, always had trouble with charging cables.