Community Port Requests

Something in 8-10" range.'

• Samsung Galaxy Tab 4 - 10.1"
• Samsung Galaxy Tab 3 - 8"

@JSE, aggregating choices to one vote-able answer biases the poll and might even conceal the intended outcome. We should rather split them to one answer each.

Agreed, only one device per answer, and let's not put specs as answers - increases complexity. If you want e.g. 8-10" range, check back regularly and upvote matching answers

Turn this into a wiki and add the suggested devices to the main post so people wont duplicate th entries so much.

But we won't know their upvotes nor respective discussions, also a maintenance nightmare

No, I don't mean that. I mean just list the devices posted as answers so there won't be 5 voting entries for FairPhone like at the last thread

@launchpad single entries please (everyone!)

@jollailija please show an working example to a TJC noob like me :-)

Nexus 6 ...

@sledges Okay, follow my lead!

@all See, that's what I mean. Isn't it pretty?

It's pretty, but I have very limited time to do such not automated work. I'd rather extend answerbot to show a list-view of all answers with preview text (first line suffice), for search function to work. Or a "Search withing this question" function; but if people are in a hurry (which normally is), neither of ours efforts will prevent duplicates from coming in

Searching RSS feed looks like an immediate option for those who search..

Yeah, likely peeps won't care and will not read/fill the list. Well, at least we tried, right?

I agree TJC lists is not best practise, but it's much easier for me to keep an eye on any duplicates, and just delete them (or confront with RSS feed myself), this would be least overhead we could go ahead with :)

Oh wow you fellows are doing proper DIT! Thanks so much, as it'd take hours for one person to follow emails and keep on updating the main post. You're really keeping this one neat and clean, and the influx of new requests will decrease with time after initial wave, reducing maintenance overhead :) Thanks again

If only it was that easy to get started with porting. Maybe you could try to improve it. This community got incredible energy if lead into the right direction!

I'll try, but it will be hard to make it easier :) The biggest problem for newcomers was HADK guide jumping all over the place, yet since 1.1.1 this has been rewritten and feedback as well as yield of new ports has jumped up quite a bit

Fairphone 2

Hi, this thread is about phones not yet supported by community ports. Fairphone2 otoh is almost fully supported.

@locusf can you elaborate more on the pure (libhybrid-less) devices. I thought all devices needed libhybris because of lack of drivers.

@launchpad is it a request for community ports or official ports?

^^ @cemoi71 .... intended as an orienting thread for ports for 2016. Good if it'll help to bring desirable community-ports into existence - even better if jolla decides / can be convinced to do official ports or realizing licensing agreements.

Motorola Moto G (1st gen 2013)

@JSE - This phone has already been listed. Please read the question thoroughly before posting answers.

Not a requiest, just some self-advertising, if you have an old HTC Desire HD, sfos mostly works now. http://forum.xda-developers.com/htc-desire-hd/development/sailfish-htc-desire-hd-t2882123

Thanks @launchpad for experts score ability, I updated the estimates, and as you can see, most ports can now be filtered according to their CM support. To check if device has a port, refer to its CM page, e.g. for Xiaomi Mi4i the bottom of summary table: http://wiki.cyanogenmod.org/w/Cancro_Info