Leagoo Lead3 kitkat not working with link2sd

[mirandam]

Hi to all,

I have a Leagoo Lead3 phone. It is rooted and has kitkat 4.4.2 installed, I also have applied the sd-fix (manually into /system/etc/permissions) to be able to access my external sd-card.

Now here comes the problem:

As this is a limited storage low end phone (512MB RAM and 800MB data space), I use link2sd with a second partition on the sd-card to have the ability to install more apps. I have quite a lot of experience since android 2.3 with link2sd and I'm able to change system settings and configurations at a shell level.

So far I installed link2sd and created the second partition in ext4 successfully. Link2sd sees the second partition as it mounted correctly.

Now if I install an app and create the link it does these steps, however, the app disappears from the app-drawer.
Checking with a root-explorer effectively shows the app in the second partition, with lib and cache folders, and also the link in /data/app, all permissions and owners are correct, but the launcher doesn't show it.
The app shows up in the setup under installed apps but with a size of 0 and without the correct icon. Also if I look at the installed apps in link2sd and set the filter to "linked apps" it doesn't show the apps in the second partition.

It looks as though kitkat doesn't follow the link in /data/app
Of course I could have contacted the developer of link2sd (I have the pro version), but I think this problem is not exactly related to link2sd, but more a question of something within kitkat that is different from 4.2.x where it works perfectly.

Anyone that has any ideas?

[aus9]

mirandam writes

like I need to find a different phone like the dogee dg450 (which indeed has 4.2.x), to be able to use link2sd

Rather than try an app to do sdcard stuff why not trick Android first?

here is how using adb.....If you want to use Android terminal you may need to be root....not tested in Android terminal

1) you put your Apks onto root of sdcard
b) untested put them in a folder

2) start adb and do this....If Windows, do as admin
with Linux with user as root powers udev rule

b) Users can not proceed past adb devices command if it is a blank line or a line with serial number is ? marks
----? marks indicates udev rule is wrong or Windows user is not running adb as Admin.
c) adb device status must indicate device, or a phone name.
offline means you did not turn phone on by normal boot
sideload means you booted into recovery and choose install zip....from sideload
fastboot means you rebooted into bootloader that took you directly to fastboot OR
you then chose fastboot mode

Code:

adb devices
adb shell
pm get-install-location
pm set-install-location 2
pm get-install-location

3) reboot phone to see if APKS installed

May not work with all phones is my get-out-jail free card

OFFTOPC I was hoping to use this method to root a SC7715 Spreadtrum phone....it did not work but I still hope. my real phone is already rooted and already allows default storage to be set as sdcard in system settings -> storage

[grungemann]

[mirandam]

@grungemann The mentioned thread relates to rooting Mediatek devices. Speadtrum devices are a different world on its own. aus9 has enough knowledge to know the difference.

@aus9 I will try your method, although there's more to just the install location. Link2sd also links the libs, dex and app data to the second partition which in some cases occupy even more then the app itself, apart from that apps that use widgets are also supported by link2sd, you can even put your default launcher in it.

[aus9]

in case you never read my reply earlier...my reply was to a different thread and has been moved.

I was not replying to your lib question

cheers

[Louis777]

[mirandam]

@Louis777 you didn't read my OP very well, I know all of that, and as I said it is about Android 4.4.x not Android 4.2.x where it work perfectly.

By the way, you made a mistake in your post, both partitions need to be PRIMARY, not active, as you said. Active is only needed to be able to boot from a partition and has no influence on link2sd.

[Louis777]

[aus9]

Louis777

interesting

light reading is
[Only registered and activated users can see links Click here to register]
this confirms your info on WRITE_EXTERNAL_STORAGE, WRITE_MEDIA_STORAGE

2) Not sure if you know that a KK is also likely to have its removeable media controlled by the Volume Daemon and hence we have
[Only registered and activated users can see links Click here to register]

3) I personally don't like vold.fstab as I was having trouble with a member with a vold.fstab while I wanted to use a traditional fstab...buts that OFF TOPIC

well in a way its not because

4) you could with a rooted phone and backup
replace the vold.fstab with a traditional
edit the init.rc for vold removal

then see if sdcard becomes rw for local user and maybe resolve mirandam's issues?

I don't know I have not tried it yet.

thanks for reading

[mirandam]

Thanks for your suggestion but as I said in my OP:

... I also have applied the sd-fix (manually into /system/etc/permissions) to be able to access my external sd-card....

which is the same as your link indicates.

---

Thanks for these more to the point suggestions, I will look into these when I have some more time (at this moment I'm a little busy).

Editing init.rc means creating a modified boot.img as /init.rc gets copied from the boot.img each time the phone reboots. I have experience in this field.
vold.fstab has crossed my mind, I will have to investigate this and is by no means O.T.