@dieharddan said in Pixel 3a XL experience:

G020G

Thank you for the advice. I have had good experiences with swappa in the US as well, but now I'm in Canada, and there doesn't seem to be a good service like that.

Hello,
Sorry if this is mentioned in the thread already, but I couldn't find it.

What is the deal with "oem unlock" / unlocking the bootloader?

I bought a device off ebay and it oem unlock was greyed out and said connect to the internet to unlock. In the end I couldn't do it, so i returned the device

Since then I've been asking sellers if the bootloader can be unlocked on 3a xl or 3a, and they are all saying "NO" . So, which ones can be unlocked or how do you do it?

@raphaelhobaik
Xperia XZ (Kagura) is in the official installer

@Manchee1017 said in Xperia XZ (kagura/F8331/F8332):

@NeoTheThird I could probably help on this matter, but I will say that I don't quite know what this all means.
Are these binaries the DRM keys?
What are the prerequisites for testing? I've already installed UT and I did not manage to make a backup of the stock DRM keys beforehand.
What will these binaries do for the phone?
And of course what sort of risks am I looking at? (because while this phone isn't my DD yet, I do want it to be soon. I don't want to brick it)

Same for me

@silvertine said in Translation in Aynu language on UT:

@joe To an itak ku=sinuma ku=itak easkay. Naa e=eramiskari ya? To an pe inkar yan.

Wow. So curious. Any recommendations on where to start with learning Ainu?

@silvertine This is very intriguing. How proficient are you in Ainu language?
I would be interested in this, and learning more about the language.

Love this! Nice work.

Any chance to get an Xperia logo?

Thanks!

@metronomicon Yes, the F5321 is now in the UBports installer

@Keneda Good thinking!

Here's the updated video:
https://youtu.be/_aocnYkQcnc

It's in the installer now. Maybe this thread can be closed?

@ressan627 I was able to get it running on Kagura thanks to Konrad's help.

Issues:

• No camera. Even with gstreamer
• Graphical performance is a bit sluggish
• No fingerprint reader
• Wifi won't automatically connect after reboot
• Phone reboots when plugged into usb attached to computer
• Using suru dark system theme causes text fields in browser to be all black with black text (i.e. unreadable)
• No flashlight

This device may show up in the installer some time, but here is what I did to get it running. Pieced together from docs.ubports.com , docs.halium.org and some documents from the telegram group: @ubports_porting

Building and Installing

If you don't want to build the images yourself, then contact me and I can find a way to send them to you.

Porting Environment

http://docs.halium.org/en/latest/porting/first-steps.html

sudo dpkg --add-architecture i386

sudo apt update

sudo apt install git gnupg flex bison gperf build-essential \
  zip bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
  libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
  libgl1-mesa-dev g++-multilib mingw-w64-i686-dev tofrodos \
  python-markdown libxml2-utils xsltproc zlib1g-dev:i386 schedtool \
  repo liblz4-tool bc lzop imagemagick libncurses5 rsync

The problem with 20.04 is that repo doesn't exist in the repositories. You will have to install the package and dependency from eoan.

Download packages:
downloaded the packages manually:

python-kerberos from https://packages.ubuntu.com/eoan/python-kerberos
repo from https://packages.ubuntu.com/eoan/repo

I then installed them using sudo dpkg -i <filename>, python-kerberos first.

It may complain about python version, but it will work.

Get Halium Source

This takes a long time and a lot of space (~15GB).

mkdir halium && cd halium

repo init -u https://github.com/Halium/android -b halium-7.1 --depth=1

repo sync -c -j 16

Manifest

For Kagura the manifest is now part of halium source. So you don't need to do anything here.

But for reference, this is what needs to be done for devices not included.
// You need to make sure the correct manifest for the devices is in:
// /halium/halium/devices/manifests

// If you don't have a manifest, then you will have to create it for your device:
// http://docs.halium.org/en/latest/porting/get-sources.html

Get Devices Source

First get devices source (pulled from info in manifest)
./halium/devices/setup kagura --force-sync
// had to use force-sync or no kernel folder would show up

Fix Mounts

Not sure. Seems not applicable to kagura

Kernel Check

Run Kernel check for Ubuntu Touch
./halium/halium-boot/check-kernel-config kernel/sony/kagura/arch/arm64/configs/aosp_tone_kagura_defconfig -w

Also ran on :
./halium/halium-boot/check-kernel-config kernel/sony/kagura/arch/arm64/configs/defconfig -w

It will fix a few things. Run it again until everything is fixed.

BUILD IMAGE

Build the image

Once halium-boot is in place, you can build it quite simply. You will also need to rebuild system.img due to our changes.

cd to your Halium BUILDDIR
source build/envsetup.sh
Run `lunch` and select the correct device
`mka halium-boot`
`export USE_HOST_LEX=yes` // fixes an error 
`mka systemimage`

Anothe 15GB or so are needed to build these things.

Installing Ubuntu Touch

Get Halium-Install

Clone this repository

https://gitlab.com/JBBgameich/halium-install

Install dependencies: sudo apt install [those packages below]
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img

Download rootfs:
https://ci.ubports.com/job/xenial-hybris-edge-rootfs-arm64/

Install Halium:
./path/to/halium-install -p ut path/to/rootfs.tar.gz path/to/system.img // using the correct paths and changed root password

After install. Reboot.

Do some fixes and updates

NOTE: I'm not sure if all this needs to be done before flashing the tone file (See last step. That might actually work as is) but if not.

Device should boot, show a purple indicator light briefly, and then hang at the Sony logo. It is actually booted at the moment.
There should be a new wired connection that shows up on the connected computer. When that shows "connected" you can ssh to the phone.

SSH:

ssh phablet@10.15.19.82

// sometimes requires a reboot first

Connect to wifi:

nmtui

Make device writable:

sudo mount -o remount,rw /

Edit and update:

sudo -i

Add Udev rules:

cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-kagura.rules

Install xenial arm 64 stuff:

ubports-qa install xenial_-_arm64

apt update && apt upgrade

apt install mir-platform-graphics-android-caf15

Change Lib path

nano /etc/environment
edited to LD_LIBRARY_PATH=/vendor/lib64:/system/lib64

Platform Apis

NOTE: I think NOT doing this allows the light sensor to work. Not sure which option is better.

comment out the if and fi in /usr/share/upstart/sessions/unity8.conf

Example:
# if [ ! -f /system/lib/libubuntu_application_api.so ]; then
initctl set-env --global UBUNTU_PLATFORM_API_BACKEND=test.so.3
initctl set-env --global UBUNTU_PLATFORM_API_SENSOR_TEST=/etc/ubuntusensors/test.sensors
# fi

Flash the Tone file

This is a key step to actually boot into Ubuntu Touch

Download:
https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-tone/

Boot to bootloader

fastboot flash oem [filename]

@konradybcio said in How to: test GStreamer-droid based camera support in Ubuntu Touch (for Halium 7.1 based port):

Getting this while trying to open camera on Kagura:

https://pastebin.ubuntu.com/p/Rykm2N66F6/

Same output for me on Kagura. Camera loads but all black.

Looks like Konrad has pretty much completed this port!
https://github.com/konradybcio/device-sony-kagura

The manifest has been requested to be merged into halium.

Hoping to build the images and see how it goes...

Living proof (of concept):
https://www.youtube.com/watch?v=UyOcQtNDZwM

@danqo6 said in Podbird reignited:

Hello guys again,
I have for you another version for testing. Restoring position should be more reliable now, I changed behavior of seeking slider and added to episode details position were you stopped listening certain episode.
Download armhf and arm64 build.

@CiberSheep Your issue should be fixed

@joe said in Podbird reignited:

• Sometimes plays, or sometimes renders the episode completely unplayable

@joe Please test if this issue still persist

Awesome it seems to be working. At first the position wasn't being remembered but I turned it off and on again, and that seemed to make it work post download. Works offline. Thank you!

I will continue testing to be sure.

@Toadtoad
You are setting up via ADB through TWRP?
Permissions should be:
-rw------- 1 root root
And the profile in /data/system-data/etc/NetworkManager/system-connections is the exact name of the wifi SSID.

Not sure how you would know if you are in the terminal or not. One way would be to assume you are, then create a file e.g. "touch testfile" . Then go back to TWRP-adb and see if that file exists.

@Toadtoad
Refer to my first post for the wifi part.
Under

[wifi-security]
auth-alg=open
group=
key-mgmt=wpa-psk
pairwise=
proto=
psk=

psk = [your wifi password]

I think you can copy the settings from another ubuntu machine under
/etc/NetworkManager/system-connections

You don't need to TAB for the password in terminal. Also it might vary for the one on the lock screen

@Toadtoad
Once you can be sure that you are past the lock screen:
UPDATE on this for me for some reason:

• Hold superkey, and press a number to open any app . e.g. settings, which will prompt for password if locked.
• Enter password ** For me I now have to press TAB to make the cursor go to the password field.

You can reach the terminal or any app by pressing:

• Superkey (this will open the dash)
• Type in "terminal" , which should search for the app. Then press Enter.
• You should be in terminal now, and it asks for your password again. Type that in and press Enter.
• Now will be in the command line

Also try "phablet" as the default password. That's what it was on my OP3.