Posts made by wgarcia

@dremelts I have an OPO also with OTA 15 stable channel and GPS works normally. It takes a while until it gets the first fix and applications start responding, something like between 10 to 15 minutes outdoors.

Another way is to put the key in a server where you have an account, and tranfer it to the device from the server using sftp.

@htc_tattoo

I'm a daily user of UT since 2016. First an BQ Acquaris E5 (model from memory), then a Nexus 5 and now an OPO. The OPO's bluetooth can send and receive phone calls from my car right now.

Only thing missing is some apps that my municipality only provides in Google Play and Apple store, with Google location services or else it doesn't work, really sad for a public institution.

@Flohack As an old advocate, and without wanting to open any debate so this is going to be my only post, I just want to say that I still miss a searchable and threaded mailing list archive, it's a pain for me each time I want to find old info in this project. But kudos anyway for all the work, I will keep looking in Telegram and the forum.

@cefre00 Better open a new post for your problem.

@tsar_chasm Yes, that solved it. Too bad so many good solutions are buried in the Telegram chats.

Also as a constructive suggestion it could be helpful to add at the Gitlab readme that current images do not boot unless you start from this one.

@AppLee I do have a serial cable, and I produced a log which you can see in the Gitlab issue:

https://paste.ubuntu.com/p/rQNQ4kgQxM/

@kugiigi dd and Ubuntu Disk Creator from desktop. I used these same two methods a lot of times before with UBports, and it is also the method I use for the other distributions, and they work perfectly fine.

Take into account that the image does start to boot, so it seems it is correctly burned, but it doesn't manage to boot.

I tried bmap as you suggested in the Gitlab issue but it didn't work for me, it produced an error, I don't remember now exactly which.

Since two weeks ago, I stopped being able to boot burned UBport images from the SD card, I've tried already 6 or 7 different images, the last one from yesterday. The phone boots fine the images of other SO (I tried Mobian, Manjaro and Luna OS and all boot fine).

I've entered an issue in Gitlab:
https://gitlab.com/ubports/community-ports/pinephone/-/issues/117

I've tried with two different SD cards just in case, but same behavior.

I also tried to clean the userdata partition, with the following steps:

Press and hold power and volume up.
It boots into "updating", but should be ignored, wrong splash.
Plug the phone into a Linux computer with the red cable.
Run:
sudo fsck /dev/sdb10

But still doing the same.

@w0lf3n I saw a case recently (last week) for installation in a OnePlueOne with similar symptoms as yours.

We solved it going back to an old version of the installer which was the one I used to install in my OnePlusOne. It is this one:

https://github.com/ubports/ubports-installer/releases/tag/0.2.6-beta

This version saw the device immediately and completed the installation without a glitch.

@AppLee Good to know. My Nexus 5 died anyway at the start button, another common issue it seems with the Nexus 5. It is a great phone anyway, I had it for more than 2 years as daily driver with UBports.

@Keneda Fixed, thanks.

@amc400 I have had both, currently using an OPO as daily driver.

OPO is a more powerful device, more RAM, but both run UBports as smoothly. Battery life is better in the OPO, the Nexus 5 had bad battery life even with the original OS.

The Nexus 5 I think is easier to install, and really hard to brick. The OPO can also be installed easily, but if anything goes wrong, I think is harder to recover.

For the OPO Bluetooth works I would say worse than with the Nexus, but there has been a patch which is being tested, I tried it and I think it improves Bluetooth a lot.

This is my opinion.

@peat_psuwit I tested this in my OPO, Ota-12, devel channel. Bluetooth is now working for making and receiving calls from my car, It was not working before. Great job!

@UniSuperBox I also was in the same situation, and could restore the standard dash by switching between channels, so I did not need a full reinstallation.

@Flohack I also need this 2FA access with an Android/IOS app to access the VPN of a major US university, which I need for my work. On the other hand, the app to pay for parking in my municipality is also only Android/IOS of course, and the app depends on Google services for location, so Anbox will not help. And we can go on and on. Unless a strong civil movement stops governments (and other institutions like universities) on relying on Google services, it is really hard to get rid of Google dependence.

I always thought the word "supported devices" brings confusion to newcomers for a while until they understand the issue. "Supported" implies some devices get support and some others could be used but they don't get support. "Ported" is a much clearer word, and once it is explained what takes to port a devices, then there is no confusion any more.

I use 2.

@Flohack Thanks a lot!