FORUMS

Changing kernel lefts some old bits

14 posts
Thanks Meter: 1
 
By ktatar156, Junior Member on 5th August 2016, 09:21 AM
Post Reply Email Thread
Hi,

I'm fighting with bug https://bugs.launchpad.net/canonical...e/+bug/1592412
In short: I've installed FlymeOS 5.1.x (which has DT2W feature). But when I flash UT again, DT2W is still working (and it shouldn't, because UT doesn't support that feature). It seems that when phone is going to older 4.x Android base (which UT has for now), it leaves some files from FlymeOS 5.1.x.

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).
Or maybe is there any possibility to disable that DT2W manually in kernel?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes