We are currently looking into supporting more devices with Plasma Mobile. Has anybody already had some success in running it on a device other than the Nexus 5?

I have a Nexus 5 but with the instructions given at the site of plasma-mobile, I'm afraid to break.

If you have not backupped data on the phone, you're right to be afraid. If you're afraid of making the hardware unusable ("brick it"), that should not be a problem, you can reflash from the bootloader.

Is there a Nexus 5 emulator I could use to run this and test things out on? Would like to play with this but I do not have a spare mobile device to use this with and would like to try and help out.

Jonathan

I could test it on an old galaxy nexus, but I need tutorial/docs about creating a proper image. Any link to share?

sebas wrote:Has anybody already had some success in running it on a device other than the Nexus 5?

I've got HTC Wildfire S. What should I do to run PM?

I have an LG Revolution that I can spare, I just need to an image for it, but it does NOT have a Ubuntu port for it yet.

Not sure, but I suppose first of all we should talk about cyanogenmod ports and libhybris(https://wiki.merproject.org/wiki/Adaptations/libhybris) when we are talking about hardware support similar to ubuntu touch, etc on android devices.

I have Jolla Sailfish OS device more or less similar to Nexus 5 (Snapdragon 400 MSM8930AB and Adreno 305), hope someday I will be able to test Plasma Mobile too (but for me Sailfish UI is great).

Also I have some chinese waterproof Lenovo S750 with MediaTek MT6589 and PowerVR SGX544, but I'm afraid libhybris will never be ported to this device.

I wonder, could we just take a Nexus 5 image from Plasma Phone, and replace the Nexus 5(kernel, libhybris, drivers), with the ones from another device that we want to port to? Or would that not work.
Also is it possible to create an image flashable from ClockorkMod/TWRP recovery, making it easier for people to install, and test?

A port to nexus 4 would be great! Libhybris and a kernel a working for this device. It should not be a lot of work to get this running.
Are there any documentation on how to port plasma mobil to new devices?

We don't have this guide yet, but I guess, given the interest, we should prioritize getting this going. I'll ask around if anyone knows how to do these device adaptions, and then we can perhaps have a few people who look into this.

I have a BQ Aquaris E4.5 running Ubuntu touch, so it would seem like this should be a good candidate?

sebas wrote:If you have not backupped data on the phone, you're right to be afraid. If you're afraid of making the hardware unusable ("brick it"), that should not be a problem, you can reflash from the bootloader.

In other words, if something goes wrong I can always reinstall Android from the bootloader, using fastboot ¿right?
By the way, updates to Plasma Mobile How come I have to OTA or flash the phone with each update?

I returned to Android. First I installed the latest version available (136) for developers. Plasma never started, I would get the typical error window of KDE.

Then I installed the version 17, and this if started, but he's too green. For starters, the calling application runs in the background and I can not close or reopen. Many of the applications that come by default do not even open.

In short, we must work hard still in Plasma Mobile, which is a shame to use as a base Ubuntu Phone, since they inherit their problems. I understand that everything is easier, as they can work together, but would have been nice to offer something different Plasma Mobile. Well ..

When a little over worked, I'll install again ..

https://plus.google.com/+ErnestoAcosta/ ... GprMg29omv

Ow, yes, it's a prototype, we know there's a lot of work ahead. It should not be so bad, however. 136 had plasmashell crashing on startup (which I think should be fixed if you just upgrade all packages). You may also try devel instead of devel-proposed, which should be the version just before 136, and not have plasmashell crash at start.

Bottom line, yes, much work ahead and we're still quite far from a phone that's usable as daily driver. (But I think we communicated this quite clearly.)