[Q] how to make the stock launcher widgets visible in other launchers - Sony Xperia P, U, Sola, Go

Dear m8s
there's no doubt that Xperis S stock launcher is awesome
but still i want to experience other launchers
for me, i found Nemus launcher is so great
my only problem is that i can't place the stock widgets (timescape) and Accuweather on any of the home screens
as it's not available in Widgets list in any launcher except the stock one only
tried some other launchers to check, and result is still the same
available only in stock launcher widgets list
and not available for any other launcher
My Q is, is there any method i could make the stock launcher widgets list available for all launchers
i'm sorry to place a Q in this forum, but i think my Q is related to this forum only
i'm not trying to break any rules
Thanks in advance.

---

You can't use Sony widgets with other launchers.

---

I've wanted this for a while but my research yielded nothing :-(
Sent from my XperiaS via subspace beacon.

---

Not possible...sorry and actually that is the reason I didn't move to other launchers...

---

i really can't believe it that Devs can cook a complete ROM
and they r unable to port some widgets only !!

---

ChIcO*GsM said:
i really can't believe it that Devs can cook a complete ROM
and they r unable to port some widgets only !!
Click to expand...
Click to collapse
You see, when you modify the stock firmware, you don't have sources for anything but the kernel. You can add tweaks and overclocking and init.d without going deeper, but after that it's all decompiling. You probably know a toolchain named smali. If you don't, smali is like assembly for Android. You can't get java code from a built app, just as you can't get C++ from an EXE. Now say we want a part of that app ( widgets ). This is the very moment smali comes in. With smali, you can get some very basic, assembly like code from a prebuilt app. That's the code Android uses to run it. And that's where the interesting things are. To allow using Sony widgets on other launchers, you need to find the code responsible for loading them, displaying them and all the code the previous two depend on. It can be in the launcher or in the frameworks, so it's two huge source trees that you can't even search through. When you get all this code, you need to integrate it into your launcher app. Ironically, Android doesn't support smali code directly, so you have to either rewrite it back into Java ( which is hard) or build your launcher first and then add the code using smali ( which is not easier) .

---

K900 said:
You see, when you modify the stock firmware, you don't have sources for anything but the kernel. You can add tweaks and overclocking and init.d without going deeper, but after that it's all decompiling. You probably know a toolchain named smali. If you don't, smali is like assembly for Android. You can't get java code from a built app, just as you can't get C++ from an EXE. Now say we want a part of that app ( widgets ). This is the very moment smali comes in. With smali, you can get some very basic, assembly like code from a prebuilt app. That's the code Android uses to run it. And that's where the interesting things are. To allow using Sony widgets on other launchers, you need to find the code responsible for loading them, displaying them and all the code the previous two depend on. It can be in the launcher or in the frameworks, so it's two huge source trees that you can't even search through. When you get all this code, you need to integrate it into your launcher app. Ironically, Android doesn't support smali code directly, so you have to either rewrite it back into Java ( which is hard) or build your launcher first and then add the code using smali ( which is not easier) .
Click to expand...
Click to collapse
in short words
i have to wait till Android support this smali
or to wait for some Dev to wast his time on this
as i dun have any other solution yet
So,Waiting .....