@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.

@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

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

Thank you!

@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 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 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 Any ideas how I might get past this "ERROR: Operation Denied" error? It seems that's what's preventing me from dropping into recovery after the kernel panic, right? and the bootloader erases pstore?

@flohack OK, that didn't work. I decided to reflash android and re-flash ubports again for a fresh slate.

During the ubports installer while it was pushing files I decided to adb shell in and look for console-ramoops. To my surprise, it was there. No idea if it's useful or not.

https://pastebin.com/zYAAZGTs

@flohack Volume down just goes into the bootloader without the error

@flohack Hmm holding Volume Up during boot drops me into the bootloader with the following error message in yellow:

ERROR: Operation Denied

Nothing in /sys/fs/pstore/, either

Maybe I'm pressing Volume Up at the wrong time?

@flohack Oh also, same usb 3-2 dmesg entries as before.

@flohack Hmmm, well now I'm in a boot loop. At least it's something different :). After the google logo I get a temporary black screen before it reboots.

And I still can't telnet

Both system and data are empty:

root@walleye:/ # ls -alh /data
total 0
drwxr-xr-x  2 root root 0 1970-01-01 00:00 .
drwxr-xr-x 24 root root 0 1972-09-20 23:41 ..
root@walleye:/ # ls -alh /system_root
total 0
drwxr-xr-x  2 root root 0 1970-01-01 00:00 .
drwxr-xr-x 24 root root 0 1972-09-20 23:41 ..

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

Oh and please see again in recovery if you can also mount system partition (mount /system_root could do it). And whats inside there...

root@walleye:/ # mount /system_root
root@walleye:/ # ls -alh /system_root                                                                                                                                                                                                                                                                                        
total 58K
drwxrwxr-x  24 audio camera 4.0K 2021-08-26 08:03 .
drwxr-xr-x  24 root  root      0 1972-09-19 23:20 ..
drwxr-xr-x   2 root  root   4.0K 2021-08-29 06:04 android
lrwxrwxrwx   1 root  root     13 1972-09-14 01:28 apex -> /android/apex
drwxr-xr-x   2 root  root   4.0K 1972-09-14 01:28 bin
drwxr-xr-x   2 root  root   4.0K 2016-04-12 20:14 boot
lrwxrwxrwx   1 root  root     14 1972-09-14 01:28 cache -> /android/cache
lrwxrwxrwx   1 root  root     13 1972-09-14 01:28 data -> /android/data
drwxr-xr-x   3 root  root   4.0K 1972-09-14 01:28 debian
drwxr-xr-x   4 root  root   4.0K 1972-09-14 01:28 dev
drwxr-xr-x 115 root  root   4.0K 1972-09-14 01:29 etc
lrwxrwxrwx   1 root  root     16 1972-09-14 01:28 factory -> /android/factory
lrwxrwxrwx   1 root  root     17 1972-09-14 01:28 firmware -> /android/firmware
drwxr-xr-x   3 root  root   4.0K 1972-09-14 01:28 home
-rwxr-xr-x   1 root  root   9.4K 2021-04-13 21:11 init
drwxr-xr-x  20 root  root   4.0K 1972-09-14 01:28 lib
drwx------   2 root  root    16K 1972-09-14 01:27 lost+found
drwxr-xr-x   2 root  root   4.0K 2021-08-26 22:22 media
lrwxrwxrwx   1 root  root     17 1972-09-14 01:28 metadata -> /android/metadata
drwxr-xr-x   3 root  root   4.0K 1972-09-14 01:28 mnt
lrwxrwxrwx   1 root  root     12 1972-09-14 01:28 odm -> /android/odm
drwxr-xr-x   3 root  root   4.0K 1972-09-14 01:28 opt
lrwxrwxrwx   1 root  root     16 1972-09-14 01:28 persist -> /android/persist
drwxr-xr-x   2 root  root   4.0K 2016-04-12 20:14 proc
lrwxrwxrwx   1 root  root     16 1972-09-14 01:28 product -> /android/product
drwx------   2 root  root   4.0K 1972-09-14 01:28 root
drwxr-xr-x  12 root  root   4.0K 1972-09-14 01:28 run
drwxr-xr-x   2 root  root   4.0K 1972-09-14 01:28 sbin
drwxr-xr-x   2 root  root   4.0K 2021-08-26 22:22 srv
drwxr-xr-x   2 root  root   4.0K 2016-02-05 09:48 sys
lrwxrwxrwx   1 root  root     15 1972-09-14 01:28 system -> /android/system
drwxrwxrwt   2 root  root   4.0K 2021-08-26 22:32 tmp
drwxr-xr-x   2 root  root   4.0K 2021-08-29 06:04 userdata
drwxr-xr-x  10 root  root   4.0K 1972-09-14 01:28 usr
drwxrwxr-x  11 audio camera 4.0K 2021-08-26 08:03 var
lrwxrwxrwx   1 root  root     15 1972-09-14 01:28 vendor -> /android/vendor

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

@agates ok can you check on your host what dmesg gives you, any mention of an RNDIS adapter coming up when booted normally?

Here's the dmesg log, from recovery (first disconnect) -> normal reboot -> force reboot into bootloader

agates@risa ~> sudo dmesg --follow-new
[73050.471900] usb 3-2: USB disconnect, device number 6
[73182.441061] usb 3-2: new high-speed USB device number 7 using xhci_hcd
[73182.589728] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[73182.589735] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[73182.589738] usb 3-2: Product: Android
[73182.589739] usb 3-2: Manufacturer: Google
[73182.589741] usb 3-2: SerialNumber: FA79F1A09215
[73186.703138] usb 3-2: USB disconnect, device number 7
[73212.553220] usb 3-2: new high-speed USB device number 8 using xhci_hcd
[73212.702787] usb 3-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.04
[73212.702794] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[73212.702796] usb 3-2: Product: Pixel 2
[73212.702798] usb 3-2: Manufacturer: Google
[73212.702799] usb 3-2: SerialNumber: FA79F1A09215

@flohack No change in behavior

@flohack I was able to boot into that image and list the data partition:

agates@risa ~/D/ubports> fastboot flash boot boot_2021-09-03.img
Sending 'boot_a' (32768 KB)                        OKAY [  0.777s]
Writing 'boot_a'                                   OKAY [  0.155s]
Finished. Total time: 0.937s
agates@risa ~/D/ubports> adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
FA79F1A09215    recovery

agates@risa ~/D/ubports> adb shell
root@walleye:/ # mount /data
root@walleye:/ # ls -lh /data
total 2.0K
drwx------ 4 root root 4.0K 1972-09-14 01:27 android-data
root@walleye:/ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=1853348k,nr_inodes=463337,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1853348k,nr_inodes=463337,mode=755,gid=1000)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /tmp type tmpfs (rw,relatime,size=1853348k,nr_inodes=463337)
tmpfs on /storage type tmpfs (rw,relatime,size=1853348k,nr_inodes=463337,mode=050,gid=1028)
pstore on /sys/fs/pstore type pstore (rw,relatime)
none on /config type configfs (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/sda45 on /cache type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)
/dev/block/sda45 on /data type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)

@flohack Still no luck here, no console_ramoops found, and same behavior with stuck at google logo.

Here's the last_kmsg if it helps.

EDIT: I attempted with both the TWRP+boot method and the ubports installer (modifying the config with that new url for boot.img).

@flohack OK, I flashed TWRP to the boot partition, booted into TWRP, wiped the data partition, then booted into halium-boot_walleye.img directly from fastboot.

Same result, can't telnet, no console_ramoops file.

Wondering if I should start from android again for a clean slate?

@flohack Okay so to be clear, I:

1. Flashed TWRP to the boot partition:
   fastboot flash boot twrp-3.3.0-0-walleye.img
2. Booted into the halium boot image directly:
   fastboot boot halium-boot_walleye.img
3. Waited 10 minutes
4. Force-rebooted the device, it booted into TWRP
5. Opened adb shell checking for /sys/fs/pstore/console_ramoops.

Unfortunately that file isn't there... the pstore directory is empty.

Here are the images used with sha256sum:
twrp-3.3.0-0-walleye.img: e7edcfb553b5c9b7ed717b3439c465075ee17b0eb938bafdce511bbea1cc3cd6
halium-boot_walleye.img: ed82425569e229863e58c17e636a2e341374d796520a478598580cbf9878127c

@flohack Both fail with network unreachable