@dobey said in Howto rebuild UBports image for specific device from sources?:

So, the rootfs is not specific to a device. Pretty much everything that can be built via crossbuilder is part of the rootfs, which you do not need to rebuild for your device. The linked "systemdev" documentation is about developing components at this level (services that run inside ubuntu, unity8 shell, system-settings, etc…).

Well, what I am looking for is description of steps that one needs to do, if he would like to try fix something in e.g. system-settings.

If what you want to build is a port for your device, the best place to start is https://docs.halium.org and the porting guide. They describe how to build the device-specific parts.

I want to understand, full development -> build -> deployment -> test cycle for supported device I have.

Known issue: https://github.com/ubports/ubuntu-touch/issues/448

@advocatux Thanks for the tip. Reinstalled 16.04 / stable. Got switcher back... Will try rc

@root-ruud said in bq Aquaris 4.5 Ubuntu Touch (vivid/ubuntu 15.04) is not upgrading.:

1
I need two SIMs, only bottom slot is working at present, but it worked under the canonical version.
This is my daily phone and my work phone, I can not miss any calls. This is a deal-breaker.

Well, works for me. I use 2x SIMs on bq 4.5 / 16.04 - rc. Probably you need to file a bug, so that you can get some advice on how to detect what might be the problem.

2
morph browser turns white spontaneously, a restart is required to get pages loading properly.

Well. Yes. There are some indications that this might be related to amount of physical RAM available on the phone. Although I do not believe that it is related to memory, since for me just reload of the page normally helps.

3
I want to know exactly how long my calls lasted, incoming and outgoing.
not visible at present

It is there. In your call history - swipe left call you want to have an info on, tap (i). Or do you mean something else?

Here is an instruction that worked for me to transfer data from Bq 4.5 to Fairphone 2

Required:

• SD-card
• Both device should have SD-card slot
• adb tools

Preliminary Steps

• Check that your SD-card is accessible on both devices
• While device is booted and connected to PC, figure out SD-card info needed for accessing it when device is booted into recovery:
  • In adb shell issue mount command
  • Note the device that is mounted to /media/phablet/<...>, example in my case

    <... -removed>
    /dev/mmcblk1p1 on /media/phablet/ubackup type vfat (rw,nosuid,nodev,relatime,uid=32011,gid=32011,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
    

    Note that device /dev/mmcblk1p1 is mounted to /media/phablet/ubackup, which is SD card in my case, expect that last part of /media/phablet/ubackup will be different in your case. Make note of the device name (/dev/mmcblk1p1).

Backup data to SD card

1. If not done before: connect phone to PC while adb is running
2. Reboot phone into recovery: adb reboot recovery
3. Acquire root: adb root
4. Activate shell: adb shell
5. In the root shell (command prompt ends with # sign)
   5.1 Mount SD card with the following command (note that /dev/mmcblk1p1 above becomes /dev/block/mmcblk1p1) :

   mount -t vfat -o flush,utf8 /dev/block/mmcblk1p1 /sdcard
   

   5.2 Backup system-data and user-data partitions (commands below will also create log files, that can be examined for possible errors) :

   tar -czpv -f /sdcard/system-data.tgz /data/system-data/ >/sdcard/system-data.out 2>/sdcard/system-data.err
   

   tar -czpv -f /sdcard/user-data.tgz /data/user-data/ >/sdcard/user-data.out 2>/sdcard/user-data.err
   

   5.3 Check created archives. The commands below should not produce any output:

   tar -xzv -f /sdcard/system-data.tgz >/dev/null
   

   tar -xzv -f /sdcard/user-data.tgz >/dev/null
   

6. Power down your device (example for adb shell) :

   shutdown -P now
   

Restore data from the backup on SD card

For me it was repeat of the sequence from the previous section but with the target device connected. The only difference was in the final step.

In principle, external card reader device may require different device name in mount command of step 5.1 options. You can check it as indicated in the Preliminary Steps section above.

Repeat steps 1. ... 5.1 to make SD card accessible.

5. In the root shell (command prompt ends with # sign)
   5.1 Mount as in the 5.1 above
   5.2 Restore data:

   tar -xzv -f /sdcard/system-data.tgz
   

   tar -xzv -f /sdcard/user-data.tgz
   

6. Reboot your device

@kugiigi Thank you for explanation. Mystery solved. I left my comments in the issue tracker.

Known issue: https://github.com/ubports/ubuntu-touch/issues/448

@UniSuperBox Well as far as I can tell, Ubuntu Touch accesses Google Account data.

On my device Address Book and Calendar apps use Google Account configured in the system settings. Their data is being synced with Google Contacts and Calendar, respectively.

Isn't Ubuntu, mentioned in the mail, that 3rd party entity, which actually links my device to Google Account?

@kugiigi Thank you for explanation. Mystery solved. I left my comments in the issue tracker.

@kugiigi, @Lakotaubp What do you mean by "special pass"?
And how one can setup, for example, Contacts to use it?

@wgarcia I understand.

So the question is, will UBports do something about it?

According to Google Account info:

Ubuntu
Has access to Gmail, Google Calendar, Google Contacts, Google Drive, Google Hangouts, Google Photos

I received the same message. What I really don't like about it is "some data" part without full specififcation:

some of the data of your Google Account, such as the content of Gmail.

I have submitted the issue to UT Tweak Tool bug tracker: https://gitlab.com/myii/ut-tweak-tool/issues/32

But it does not seem to be reproducible on other's people FP2 devices.

Could someone try the following in UT Tweak Tool:

• Set Scaling - Grid Unit to some non-default value, let say 26
• Accept Unity restart
• Set Scaling - Grid Unit to default, via "Restore default..." item. Warning: for me it was set to 13 and I had some difficulty to set it back. Although reboot of device seem to restore decent default of 23.
• Report your findings here and if you can confirm the issue - directly in the issue report linked above

Thanks.

The instructions you are referring to are aiming to backup all data needed to restore system to previous condition (excluding operating system itself, I believe). It looks like it worked for some people, not for me, though.

But it helped me to make backup of all data my own way, including system settings (now my Fairphone even presents itself as "BQ Aquarius 4.5", when connected via BT ).

Back to the instruction.

system-data and user-data are visible in /data only when your device is booted in recovery mode. When system is booted normally they are accessible via different location.

That is:

1. Connect your device to PC
2. Run adb devices (output should list your device as recognized)
3. Run adb reboot recovery

Now you should be able to do adb shell and listing of /data should show these folders.

At this point your adb pull of both should be fine.

I used adb from Ubuntu 19.04 repositories:

$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5
Installed as /usr/lib/android-sdk/platform-tools/adb

$ apt-cache policy adb
adb:
  Installed: 1:8.1.0+r23-5
  Candidate: 1:8.1.0+r23-5
  Version table:
 *** 1:8.1.0+r23-5 500
        500 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages
        100 /var/lib/dpkg/status

Concerning root: I had to explicitly request it on Bq 4.5. On FP2 adb shell was with root access enabled by default.