ubuntu-phone team mailing list archive

[Krzysztof Tataradziński <ktatar156@xxxxxxxxx>]

Thanks for clarification! I'm thinking that in latest Flyme OS 5.x
kernel there are some bits responsible for DT2W, but are disabled by
some config/script itself (beause in FlymeOS GUI there are no such
options to manage DT2W).
That log
https://launchpadlibrarian.net/266876187/syslog
shows (ctrl+f and find 'double') that there is something left from
FlymeOS kernel in UT installation and not removed/overwritten by wipe
option. Maybe I sould remove some specific file reponsible for DT2W?
How to find it?
If I good understand, whole UT installation (and other ROMs)  do sth
similar to below process:

Android files before UT install:

a
b
c
d

UT files in image:

a
b
d
e

so the result (UT image installation) will be:

a (version from UT image)
b (version from UT image)
c (from Android before installation)
d (version from UT image)
e (new file from UT image)

yes? Simply it works like copying and overwritting all files/folders,
but if in destination there are more files not included in source
path, installation will leave them untouched (don't remove them),
right?
Is there any possibility to fix that (remove these additional Android
5.x bits)? I mean to get something similar to 'rsync --delete' (it
sync and delete files in destination which are not present in the
source).

Best regards,
Krzysztof Tataradziński

2016-08-04 22:14 GMT+02:00 Michael Zanetti <michael.zanetti@xxxxxxxxxxxxx>:
> Hi
>
> On 04.08.2016 22:01, Krzysztof Tataradziński wrote:
>> Hi,
>>
>> I've started fighting with bug
>> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592412
>> good news is that I have access to all /* folders and files. I'm
>> thinking about removing whole kernel and others files. Does 'rm -fr /'
>> safe? Will my phone boot into fastboot after that, and next (after
>> flashing recovery) install UT? Does UT rom installed by
>> sudo ubuntu-device-flash touch --channel=ubuntu-touch/stable/meizu.en
>> --device arale
>> contain all files needed (kernel, dev, etc.)?
>>
>
> I don't think you should do that. This will not fix your issue and
> probably cause troubles. You can try to reflash, but do not manually
> delete the files first (flashing will delete all the things for you, use
> --wipe for that).
>
> If it is true what that bug says, that you had android on the device and
> this feature was enabled with that, my best guess would be to flash
> android again, disable it in there, and flash back to Ubuntu. Sounds
> like this setting is kept in some chip-memory where we don't have the
> tools (or information) on how to change it.
>
> Good luck,
> Michael
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>