Posts made by BodoW

@ernest said in One method to encrypt /home/phablet:

@trainailleur
Lomiri cannot restart thus the screen remains black, while ssh access works fine.

I ran into the same problem on my Nexus 5.
The solution is to lock the screen (Power Button) before initiating the force-reload.
For some reason lightdm does not come back when it was shut down while the display was lit. (It took me quite a while and several WTFs to stumble over this. )
Thus my script is as follows:

#!/bin/bash

cryptsetup luksOpen /home/phablet.img phablet
e2fsck /dev/mapper/phablet
mount /dev/mapper/phablet /home/phablet && \

echo "Lock the screen now!"
echo "Restart in"
for ((t=5;t>0;t--))
do
	echo "$t s"
	sleep 1
done

cd /tmp
nohup /etc/init.d/lightdm force-reload </dev/null >/dev/null 2>&1 &

There it is

Thanks for the hint. I changed

• Copy newandroid.img to /home/phablet/anbox-data/

to

• Copy newandroid.img to /home/phablet/anbox-data/ on the phone.

That should make it clear.

I didn't specify the way I copied the files. You can do it by adb push, or, as I did, copy to/from the Nexus' Download directory via drag-and-drop and shell commands.

Or did I miss something?

I use a Bluetooth keyboard for my Nexus 5 and as long as it is in Ubuntu everything is fine. However, since it has a German layout, things get messy when you use it in anbox as there is only an English layout available.

So, here is what I did:

• Own a Ubuntu PC.
• Copy /home/phablet/anbox-data/android.img to your desktop system
• Mount the image (if you transferred it to your desktop's Download folder a simple double click might do the trick)
• Copy the content to an empty directory (lets call it newandroid_img)
• Go to newandroid_img/system/usr/keychars
• Delete all .kcm files except virtual.kcm
• Download the appropriate .kcm file from here and put it in the system/usr/keychars directory and rename it to Generic.kcm
• Do a "chown -R 100000:100000 newandroid_img
• Create a new image by "mksquashfs newandroid_img/* newandroid.img"
• Copy newandroid.img to /home/phablet/anbox-data/ on the phone.
• Reboot your phone into recovery mode
• Connect your phone via "adb shell"
• Go to /data/user-data/phablet/anbox-data/
• Do "mv android.img oldandroid.img" (Just in case)
• Do "mv newandroid.img android.img"
• Reboot

That should be it.
It could be that you can replace the images in a freshly rebooted system as well, but the revovery method appeared to be the safest to me.
Have fun with your äöüßs! (or çs if you feel like it )

I found out, how to do it. I will start a new topic for that.

I'm using a physical keyboard on my Nexus 5. Unfortunately in anbox the standard keymap is English whereas my keyboard has a German layout.
Now I found [1], that anbox can be forced to use an alternative layout if you exchange the .kcm file [2] in the appropriate directory. (In my case: ...anbox-data/rootfs/system/usr/keychars/).
Great, if I could only do file operations in this directory. It seems like this portion of anbox is an unchangeable mounted image. Thus my quest ends there.
Anyone got an idea how to overcome this limitation?

[1] https://github.com/anbox/anbox/issues/253
[2] https://source.android.com/devices/input/key-character-map-files

Thank you @Ingo. I've added it to the code and it works.
As this is the reboot approach I'd still leave the issue open as maybe someone might come up with the preferred refresh solution.

@ThrillSeeker
Good to know that someone else considers it useful too. Thank you.

EDIT: Workaround was appended to the script (last three lines)
Unfortunately WhatsApp is still neccesary to have as most people are totally incapable of grasping the concept of alternative programs. Well, here we go.
As I'd like to sent a photo from time to time I wrote the script down below and have a cron job running to synchronize the Android DCIM directory with the UBports side every minute.
This works great, however the Android side completely ignores any change in the DCIM directory. Only after a full reboot of the phone the files are in the gallery.

So the question is: Do you have any idea how to force anbox to notice the changes? "Rebooting" anbox would be ok for the start. But how?

import os
import stat
import shutil

refresh_flag=0 
ubports_dirname="/home/phablet/Pictures/com.ubuntu.camera/"
android_dirname="/home/phablet/anbox-data/data/media/0/DCIM/"

# Copy new images
ubports_filenames=os.listdir(ubports_dirname)
android_filenames=os.listdir(android_dirname)

for ubports_filename in ubports_filenames:
	try:
		android_filenames.index(ubports_filename)
	except: # If file is not yet in DCIM
		if not stat.S_ISDIR(os.stat(ubports_dirname+ubports_filename).st_mode): # Ignore directories
			shutil.copy(ubports_dirname+ubports_filename, android_dirname)
			os.chown(android_dirname+ubports_filename, 1023, 1023)
			refresh_flag=1

# Delete deleted images
ubports_filenames=os.listdir(ubports_dirname)
android_filenames=os.listdir(android_dirname)

for android_filename in android_filenames:
	try:
		ubports_filenames.index(android_filename)
	except: # If file is deleted
		if not stat.S_ISDIR(os.stat(android_dirname+android_filename).st_mode): # Ignore directories
			os.remove(android_dirname+android_filename)
			refresh_flag=1

if refresh_flag==1: # If something changed "reboot" the anbox
	os.popen("anbox-tool disable")
	os.popen("anbox-tool enable")

Did you try to mute and unmute at the beginning of the call?
The symptoms that you describe sound quite familiar. There is a bug with the microphone in the phone app which starts it kind of muted. Thus it works but poorly. Then after muting and unmuting the sound is normal.

Edit: And of course I have exactly this problem too.

@htc_tattoo i think ive read about this before. also I was the victim of this behavior myself.
quick and dirty workaround: mute and unmute. this seems to fix the problem for the moment .

About the screen problem:
I had the same problem, when I was on the train and charging the N5 on the wall socket.
I think the problem was me charging on the Butt-Pants-Seat interface as well. As soon as I touched the protected earth wire of the socket (grounding myself) everything worked fine.
Later I realized that the shielding of the cable was broken. I replaced it and hence forth I didn't have problems any more.

No, don't change it. But if you changed it in the past, this problem, or at least something similar, might happen.

Had the same problem on my N5. https://forums.ubports.com/topic/2271/nexus-5-update-to-ota-7-ends-in-recovery-solved
Did you change the /var/cache/apt/ directory?

OTA-7 update is here on my settings tab. Yeah!
After pushing the "Install" button the device reboots into recovery, shows the "installing updates" screen and finishes in the recovery menu.
After rebooting the version is still OTA-6 and the settings still shows the pending update. Not so yeah!
...

As I was writing this the typical "It can't be that petty thing" thought crossed my mind. And yes, it seems like my soft link from /var/cache/apt/ to /userdata/.... was inhibiting the update.

So I undid the link, restarted the installation, and now everything works fine.

I didn't retract my post, because there might be more wise guys like me who did the same thing and might run into the same problem.

Thanks for the information / advice.

I can't believe that after more than an hour of search requests I cannot find a solution to the simple problem: I installed pdfjs, and now I have to chose in filemanager what app to use to view a pdf. (And I don't see all apps there just pdfjs and Open Store,)

Simple question: How can I make it open the pdf by pdfjs by clicking on it? Or more generic: How do I change default apps?

@marc_aurel You're right. Sorry, I didn't have a shell open when I was writing my response and didn't remember that you had to "sudo su" or "sudo -i" first (as @matteo mentioned). I'd prefer this way as I would have a bad feeling about 777ing a directory permanently.
Besides that: Does it work now?

@marc_aurel Storage is in ~/anbox-data/data/media/0/