Related
Dear friends and fellow XDA members​
XDA's motto is, and has always been, "By developers, for developers". I think this post (click), even if old, represents perfectly what I'm trying to say.
What kyphur wrote back in 2008 still holds some truth in 2015 -- many people roam this Forum without really diving into the background of the tweaks, ROMs, or custom kernels they're using. Some that do try and investigate though, reach a dead end when the answer they are looking for is so complex and hard to find that even some developers find hard to answer in a concise private message. Some of these people, individuals with promising potential, give up because of this.
What I've set out to do is to compile a database regarding Z3C boot images and everything that has anything to do with them into one single wiki, creating a reference guide for newbies and experienced tweakers and developers alike.
The information available right now about this device's boot images is mainly centered towards older devices, or devices on a different architecture altogether. My point being that data is, for the most part, scattered and hard to find. The project will aim to rectify this issue and bring all the information under one roof
Everyone is very welcome to contribute and see for themselves, and I thank everyone who shares this project in advance. If we are to ever see this project to the end, publicity and community cooperation is important.
Should the project grow big enough, if may be expanded to cover more of Sony's lineup, or even other manufacturers' devices, along with information on system parts other than the boot image alone.
For now, the few wiki pages I have created can be found on http://bit.ly/z3c_wiki. I apologize for any mistakes I might have made, as this idea is new and the current available pages semi-rushed.
Thanks to everyone for reading!
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Yay!
Sent from my LG-H811 using Tapatalk
Hnk1 said:
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
Click to expand...
Click to collapse
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
v1rk said:
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
Click to expand...
Click to collapse
aaronrw said:
Yay!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
sweetrobot said:
about ****ing time!!! so sick of the nonSense...
cm / aosp / aokp ftw.
paperweight for the last couple of months. tried a bunch of the existing roms, just not my cup of tea.
Click to expand...
Click to collapse
k1moe said:
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Click to expand...
Click to collapse
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Hnk1 said:
DEVELOPMENT PROCESS
INTRODUCTION
I am starting this forum in hope of educating my readers about ROM development according to my experiences. Further, I will highlight what is the usual developers' thought process before they decide to build a ROM for a specific device. The reasons why they usually choose a certain device or why they prefer one device over another would also be stated briefly. I also have intention of looking into ways how we can speed up ROM productions for any device and what you can do to play your part.
I UNDERSTAND YOUR FRUSTRATION FOR NO CUSTOM ROMS EVEN AFTER SOME MONTHS BUT THIS DOESNOT GIVE YOU THE RIGHT TO SPAM
I am sure many of you must be really disappointed by the lack of development for your device and I know this must be frustrating when we see other devices are getting ROMS so quickly. I know many are too excited when they find a little about any OTA/ Custom ROM and sharing such news is fully justified. However, it's beyond my logic & thinking why the forums are SPAMMED for any little information they might find anywhere regardless of their sources or if it has been ALREADY POSTED. I reckon many of these threads could have been avoided by simply searching in the forum.
ROM DEVELOPMENT
I can assure you that many develoeprs are working very hard to PORT and develop different ROMS for a device. However, the reason we can not see any CUSTOM roms till yet is due to complicated nature of a device itself.
Usually developers prefer a device which is :
1. Easy to work with, less complicated to code with or in other terms DEVELOPER friendly. For example, for a while I had a real issue with HTC phones as they have too many things to work with like Bootloader, S Lock, Radios, Hboot version etc while in Nexus devices you only need to unlock your device with one fastboot command. That's all and you are ready to flash ROMs.
2. Personal preference of Device. This simply means that we all have different tastes and thus we choose different devices. A certain developer might only work for a certain brand while other might work with few brands. This has nothing to do with anything but a personal choice.
3. A device that promises reward in terms of money/self satisfaction. Developers usually go for devices which have most active users so if their intention is also to get some money out of it in terms of donation, this will work well with devices which are more in number.
4. Knowledge about a certain brand more than another.
5. MONEY TO BUY A CERTAIN DEVICE/DEVICES. Suppose a developer wants to make ROMS for Xperia L/ SP/Z and Xperia U. Yet he only has 500 dollars to choose from. He then will have to make a choice between devices and this will eventually mean that not all of the devices get the same treatment. Money is the most decisive factor why a developer doesnot chose your device but rather another. For example purpose only, if I have to choose between devices, I might prefer SP over Xperia L as I can see more future of SP than Xperia L(I might be wrong).
6. Simply he bought a device or it is gifted/donated to him
SOME REQUESTS
Please STOP bugging developers by trivial questions. Just think how many other people ask the same question and it gets very frustrating to actually work on the device itself.
Every developer has a LIFE apart from developing ROMs. They also have a family, school, work, hobbies, bad days and so much like us. So they will do it when they feel like doing it. Just sit back and relax. Enjoy your device until developer releases the ROM for your device. Asking a REASONABLE question seems plausible but asking same questions/useless questions without using brains is just STUPID. Kindly refrain from that.
If you have seen a developer who has taken the initiative to work on your device , the best thing to do is to be patient. Let him concentrate. Spamming and spamming again won't help really.Yet some users start SPAMMING developers, their twitters, blogs and accounts. That's really sad. You can discuss on the forum what you think about it but IRKING developers isnot really cool.
WHAT CAN YOU DO TO HELP DEVELOPERS AND SEE CUSTOM ROMS.
1. Search the form first and look for answers. DON'T start new posts/questions/threads when it is ALREADY mentioned in some other section.
2. STOP PMing/SPAMING developers but rather ask a question WHICH havenot been asked before in the forum. Do not engage in the habit of making a new forum for everything. Try to keep threads as little as possible.
3. Follow developers and see what they have updated about on their official twitter,facebook,etc rather than bugging them on different forums/social websites.
4 DONATE THEM. DONATE THEM . DONATE THEM!
The amount of efforts they put, sitting for hours in front of their PCs and I know how frustrating it gets when you try to run commands and everything seems to work yet you can not boot up your ROM. And worse, you can not find WHY really. Just a change in line in build.prop results in failure of ROM to boot up and specially working from source to build ROM is really really tough. The best thing you can do is being supportive and patient !
A ROM development requires not just EXCESSIVE amount of hardwork, time, energy and dedication but also they need MONEY to actually buy devices and try it on. They are happy and encouraged to keep on developing ROMs when they see their efforts are not wasted and they are rewarded and respected for what they do.
SOME BASICS OF ROM DEVELOPMENT
Usually this is required to make a full custom ROM
Blobs which contain hardware information which comes from hardware manufacturer like Qualcomm in case of Snapdragon processors
A fully functional device tree
Latest Android source (Or the android version source you want to build for)
Specific Custom ROM coding which is based on Android Source
Usually a device tree and kernel tree is needed before custom roms can be made available. This is a long trial and error process in which every component of hardware is made functional as usually manufacturers do not provide any code for their devices and thus new code is to be written which is very frustrating and long process!
Click to expand...
Click to collapse
Hnk1 said:
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Click to expand...
Click to collapse
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Thank GOD
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
I'll be happy to donate
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
v1rk said:
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Click to expand...
Click to collapse
Cheers for side information. I know the developer and I'm pretty sure you'd get a kernel and Cm12.1 pretty soon.
Actually I Would let the developers sort out their differences themselves, for me it is Cm12.1 coming pretty soon.
agentfusion said:
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
Click to expand...
Click to collapse
Whhhaaatttttt?!?!?! Miui?!?!?
Wait
Galaxysm said:
Whhhaaatttttt?!?!?! Miui?!?!?
Click to expand...
Click to collapse
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
agentfusion said:
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
Click to expand...
Click to collapse
Nice I can't wait!!
Nice to see this coming ... And for MIUI I haven't been able to use it since I change my original EVO ... It would be great to have it as an option ...
Great news
Daily reminder that CM12 is a desperately needed and coveted thingy for the m8+1.
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
vegetaleb said:
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Cm12.1 is lolipop 5.1
Anyone knows the progress on this...
epedrosa said:
Anyone knows the progress on this...
Click to expand...
Click to collapse
Be patient. The OP says "within a month" and it has only been roughly 2 weeks
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
apollus said:
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Thundery Steak said:
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Click to expand...
Click to collapse
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
apollus said:
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
Click to expand...
Click to collapse
I would really try not to do it on OS X. You need a proper Linux distribution to use, seeing as you're going to be following HADK very closely. It's not doable on OS X system and will never be. You require a Linux system to build another Linux system. If you went through HADK multiple times, you would know this.
I see why you think that OSX and Linux are alike, but they're really not, even when they are both UNIX systems. OS X is bastardized UNIX system and doesn't contain the GNU toolchain and the only thing it shares with Linux is the UNIX core.
Thundery Steak said:
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you..
Click to expand...
Click to collapse
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
mal-, how is your port of sailfish for the xperia pro working out?
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Thundery Steak said:
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Click to expand...
Click to collapse
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
apollus said:
mal-, how is your port of sailfish for the xperia pro working out?
Click to expand...
Click to collapse
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
mal- said:
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
Click to expand...
Click to collapse
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know...
I'm probably gonna end up putting fedora on this machine and start trying to learn to use linux (to port). Will be taking a UNIX/Linux intro class soon anyway, so that will come handy.
I am really sick and tired of boring old android and I think the effort to get Sailfish is well worth it... Gonna keep checking into freenode to see if people mention the Z3C.
Mal, thanks for your posts.
apollus said:
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know.
Click to expand...
Click to collapse
It depends on the person doing the porting at how early stage they add the information to the wiki page. Some do it very early some wait until it's reasonably usable. Of course it would be nice to have information about all ongoing porting activity.
Hi,
I just thought it could be worth mentioning that there's a device request thread on Cyanogenmod forums for our beloved Idol 3 :
http://forum.cyanogenmod.org/topic/111850-alcatel-onetouch-idol-3-55/
May I suggest that everyone who wants a Cyanogen rom to be ported on our phones should take a minute to register there and add their voices to the request ?
There's already 24 posts in this thread
Already demanded it
Cool
Just made a post, but later found out that posting a request for CM does not guarantee anything. In the sticky it states
Now, what does this mean to you? First off, requesting anywhere in the CM forum, the CM Blog, or the Facebook/Google+/Twitter accounts for device XX to be supported is probably a waste of your time and anybody who reads said request. CyanogenMod does not work on device requests as there is no guaranteeing that a current CM maintainer is even interested in the device. Additionally, its not as simple as 'porting' code, the device trees must be coded from scratch and made to work with the AOSP sourced code and CM enhancements. This takes a large amount of time and effort, especially when the device's OEM fails to release the latest version of Android for it. Second, in hoping a worthy developer sees the post and decides to take up the project... well, that is probably just wishful thinking. Many developers do not like interacting with end users (too much finger pointing between both devs and users or anger directed at the devs for something working other than how the user expects - it happens far too often); because of that, many developers don't frequent the forum (or if they do, they only view the forums for the devices they maintain).
The best way to get a device official support is not requesting it from the CM team, but learning how to do it yourself or encouraging a maintainer of an unofficial build to submit their code for review. Many developers will work on unofficial ports on the xda-developers forum, so that would be the first place to check out. If there isn't any work currently being done, you can attempt it yourself. There is a pretty in-depth article in the wiki explaining a lot of the steps of porting a device (as the bottom of the wiki states, nothing can cover every single process of porting, but it is a really great start).
Click to expand...
Click to collapse
So it would need to be someone willing to take the time out to buy an Idol 3, if one has not done so already, and then port the code for our device out of their free time. And considering the userbase for this phone does not seem all that large to be noticed, I'm not sure if CM will work on our phones anytime soon.
Well thank you very much for your posts and your research.
I'm afraid you're right, but we had to ask
Let's not lose hope too soon anyway, the fact that the device request thread exist seems to be a good point. I don't know if any device had received a CM port because of this thread, but... why not ?
I've red that Alcatel and cyanogen had been in contact for a tablet. The project has been cancelled but this might suggest they could have access to resources that would ease their work (pilots ?).
Original rom on the idol is pretty much stock Android, this is a good thing too (well I'm not a developer but I guess it's easier when it's close to the original).
And, like you said, even if the user base is not that large, chances that someone from cyanogen got seduced by the idol (like we did) are still possible... (this is the moment where everybody crosses their fingers ).
Anyway thanks again !
The thread has now 31 posts (ah no, 32 webgaffeur just added his voice !)
Thanks to all the people that took some time to post there, let's not give it up : it's time to flood the forum !
i had posted the github with source for the phone but no one seems to respond not even one single admin? we can ask other devs crdroid pacrom dirty unicorns paranoid etc.
Alas, I think Brian is right : it's probably a waste of time posting on the device request thread
I checked devices with a lot more posts and views than ours and... nothing from a dev (like huyawei and Asus zenforce 5).
Asking to other rom devs will probably be useless also. Our only hope is that a competent developer buy an idol and start working on it... If this happens, I'm pretty sure he will share his work on XDA.
Well, meanwhile we already have root, twrp and xposed working, so I guess the best thing to do is to customise out phones till it suits our needs and that's all.
Let's hope also that Alcatel will continue to push updates (marshmallow ?)
Anyway thanks for your efforts Gecko.
Sorry, didn't mean to rain on anyones parade. Just wanted to let everyone know what the stickied thread on the CM forum for device requests stated. I'm not saying it won't ever happen, just that it might take some time to get a valued reputable dev who owns, or wouldn't mind purchasing the Idol 3 and working on it for us. Most dev's accept donations of devices that want development on from the users, so if we were able to locate and contact a reputable dev, asking them if we were to provide them with the device, would they mind porting or creating a ROM for it. It's worth a try. Maybe start a bounty or fundraiser etc. I myself do not know of any dev's that would be willing to work on this device as the ones I do know of have only worked on Samsung devices.
I don't know any dev at all
P.S. : thread has 34 answers now !
Cannadoux said:
I don't know any dev at all
P.S. : thread has 34 answers now !
Click to expand...
Click to collapse
theres always other devs like pacrom paranoid android crdroid and omnirom even dirtyy unicorns
Good news, it seems we haven't hoped for nothing : http://www.cyanogenmod.org/blog/releases-releases-releases-august-2015#comment-2229134454
Thanks to @purple.epod for posting the news.
From cirwl himself : "A couple of us have one, and kernel source was just released, so strong possibility of yes"
Yiiiihaaaa
this is great i hope that we get a nightly soon
Hola
I am not a developer, but like those with a little time and technical know how, I can compile my own ROM from sources. This was extremely popular when I had the OnePlus 1 device and CM was still around.
The question is what does it take to create custom ROMs? ...especially given that OnePlus has traditionally been developer friendly with releasing not only kernel but firmware sources rather quickly compared to other OEMs. I understand that the OnePlus 3 / 3T sub-forum on XDA even outrival's the Pixel devices from Google. Maybe my inquiry is best suited in the general Android sub-forum on XDA.
That aside, I am surprised we haven't heard much from some developers who run and maintain well known custom ROMs such as LOS, RR, Mokee, DU, AICP, AOSP, etc. regarding support for this OnePlus 5. Am I missing something or it rather just a matter of time
Lastly, and more importantly, my greatest appreciation to all developers, cooks, maintainers, and others who help keep the community alive and well. Without these folks we would just be regular consumers being forced to use what crappy software we are provided with. Thanks to you :highfive: