/home/phablet directory not present?

[Chester]

Hello,

I'm currently using a OP5 and would like to develop apps for UBports. To do this, I'll have to use 'clickable' the dev tool for UBports, and to connect my OP5 to my computer. There are two ways to connect to the phone through a computer: usb with ADB or wifi with SSH. In both case, it seems that I'll need to access to the /home/phablet directory of the device.
My problem is that this directory isn't present in my device when I check through adb (device in recovery mode). When I boot back in normal mode (adb isn't working on a OP5 in normal mode) and check with the UBports terminal, the /home/phablet directory is present!? Do someone knows about that mess?

Thanks for your help

[kugiigi]

Does your device work normally? Because it's impossible that that directory isn't present because that's the home directory. Also, why do you need to access it for app development?

[Chester]

@kugiigi
Yes, my device is working normally. It's my daily phone.

Unless I'm wrong, clickable needs this directory, because it's looking for it when it's pushing the compiled program to the target device. The alternative is to set and use a ssh connexion with clickable, but in the UBports documentation for SSH, you have to connect to the target using the phablet id (phablet@deviceIPadress)...

[kugiigi]

@chester I'm pretty sure that directory is there. What is exactly the error you're encountering? I suggest just setting up SSH for ease of use I personally haven't tried ADB in a long time. Using SSH on clickable is very easy: clickable --ssh <IP>

[mateo_salta]

@kugiigi won't see it like that in recovery i think, will be in the data partition? and have to mount it i guess in recovery ( I'm not sure recovery's adb will work for devloping via clickable)

since adb is not working maybe try ssh?

or have you enabled developer mode in system settings -> about ?

[Chester]

Thanks for your replies.
I activated ssh on my OP5, then tried to connect to ssh through the terminal of my computer, using the command 'ssh phablet@deviceIP'. I got the answer "permision denied (publickey)".
As I said previously, I tried to follow this guide on the UBports documentation, but I can't do the 'configure your device' chapter because of lack of the home/phablet directory. That's why I got a mess with the public/private ssh keys... :zany_face:

[jonius]

@chester could you please paste the exact error message you are referring to? Btw, if you struggle pushing the SSH key via ADB, you can use other means like MTP or sharing it via a messenger.

[arubislander]

@chester Hi,

What version of Ubuntu Touch are you on? 16.04 or 20.04?
Have you enabled Developer mode on your device? Without it ADB will not work. In 20.04 I noticed in passing that the device wouldn't even show up on the computer desktop without developer mode being on. But I need to double check that to be sure.

[Moem]

Device page for OP5 says:

Might that be the problem?

[Chester]

@arubislander
Hello. I'm using a 16.04 version, OTA-24. Dev mode is on, udev rules ok, but nothing is shown by the 'adb devices' command in the terminal.
In recovery mode, adb is working...

[Chester]

@jonius
I didn't think about MTP. Let's have a try this way...

[Lakotaubp]

@chester adb works in recovery, try fastboot devices in Bootloader.

[Lakotaubp]

@chester MTP works for me on mine. You might need to UT Tweaktool from the OpenStore to manage things.

[Chester]

I finally managed to get it working. Thank you all for your help and advices.

To do so, I used usb with MTP to transfer the ssh public key file generated on my computer to my OP5. After that I used the terminal on my phone to manipule files and folders using the phablet account. Note that this account seems not present in recovery mode.
I followed the chapter 'configure your device' on that page, turned the wifi on, and enabled ssh.
Now the ssh connection is working fine. I can now use the clickable --ssh option the develop on my OP5.

Again, thank you all!!