@flohack

Thanks for looking at the bug and finding a fix so quickly. You guys are awesome.

Mark

@yannesc This is probably RCS. I had this issue also.

I disabled the Chat Features in the stock Android Messaging App.

Messages >> | (Hamburger Menu) >> Settings >> Chat features >> Enable chat features

Mark

I have a Pixel 3a which I was running on the Development Channel. After creating the 2 APN's 1 for internet and 1 for MMS, I was able to send/receive SMS/MMS/Calls & data via LTE worked. I think that was on version 240, and it ran pretty stable for a few days. After updating to version 244 & then 246, I was unable to receive SMS/MMS although I could send SMS (I didn't tryp MMS). I was also only able to get about 18 hours of use with light to moderate use (mostly internet browsing and some texting, minimal calls).

I've since gone back to Android as I need my phone to work.

I'm in the U.S. using StraightTalk on AT&T.

I'm willing to re-install UBports to assist with troubleshooting.

Mark

@fredldotme Is there a way to install version 0.9.6 (which doesn't depend on the Online Accounts feature) and manually create the necessary credential files so we can get GhostCloud working on PinePhone? It would really be nice to have access to my files, contacts, and calendar on my Nextcloud server.

Thanks.

Mark

@richzrich Do you have adb and fastboot installed?

On the PinePhone there are 4 update channels, the 3 usual plus the kernelupgrade channel.

• Which channel has the latest development packages? I'm especially interested in the kernel and ofono upgrades that were talked about in Q&A 98 on 10 April which will provide a more stable cellular modem connection.

• Where can we see package (kernel,ofono) changes as there is little activity in gitlab?

Thanks to all of the UBports contributors.

@moem Thanks. I'll be doing some reading at Rebble.io and then visiting Ebay.

Mark

@hexis

That is where Jumpdrive comes in.

• Burn the jump drive image to an SD card.
• Put it in your Pinephone and boot the phone.
• Connect the Pinephone to your computer via USB.
• Your computer should now show 2 external drives. - One is the SD card, and the other is the internal eMMC.
• Burn the Ubuntu Touch image onto the internal eMMC using Etcher or dd.
• Disconnect the PinePhone from your computer.
• Power off the Pinephone.
• Remove the SD card that has Jumpdrive on it.
• Power on your Pinephone
• Enjoy Ubuntu Touch.

@flohack I can confirm that my Nexus 7 2013 Flo on Release Candidate OS build number 2022-W06/1 the issue is resolved. - Morph-browser is working.

Thanks.

Mark

Please give us the old color scheme. Wow, this is hard on my eyes.

@triplemaya

You don't see the arrow on the right side of the text entry box?

I recently discovered the droidian project which is also using libhybris and halium. Is there any collaboration between Ubuntu Touch and Droidian.

@Pingu
Via fastboot flash an appropiate recovery and dtbo image.

I would use a TWRP recovery image, and a dtbo image from LineageOS.

fastboot flash recovery twrp.img

fastboot flash dtbo dtbo.img

Without flashing the dtbo, you won't be able to boot to recovery.

Please give us the old color scheme. Wow, this is hard on my eyes.

@chris_bavaria
Sorry, I for some reason thought you were on 20.04. I'm surprised that systemctl commands work on 16.04 which uses upstart hence the service command.

Is something else using the port 22? Does the netstat command work? - I don't have quick access to a Ubuntu Touch install at the moment so I don't know if that command is available.
netstat -tulnp

@chris_bavaria

systemctl enable ssh means to start the service at boot time. So if you reboot the phone after entering that the ssh server daemon would start.

But, you don't have restart the phone to start the ssh server daemon, you can just enter
systemctl start ssh

If you want to do that in one step you can enter
systemctl enable --now ssh

@helium75

Did you mean to say that Fluffychat doesn't support encryption as in end-to-end encryption?

Fluffychat DOES support encryption. Checkout the information in this forum post.

Mark

@777funk In the US, all of the providers have turned off 3g service and voice over LTE (VoLTE) is required for voice calls. Ubuntu Touch currently does not have VoLTE.

Search the forums for VoLTE to see the discussions.

Maybe there is a bug preventing the OS from powering off the device.

Can you boot to recovery or bootloader and power off from there? That would help determine if it's a hardware or software issue.

Aren't all of the tablet Home Assistant dashboards just an Android tablet in kiosk mode with just the browser running?

I don't know if Ubuntu Touch has a kiosk mode, nor if you could lock it down to just the browser.