As CM has switched to universal builds for the Galaxy S4, are there any plans to do this here at omni as well?
Chartmän123 said:
As CM has switched to universal builds for the Galaxy S4, are there any plans to do this here at omni as well?
Click to expand...
Click to collapse
Plans: yes
Active maintainers: not right now, jake sold his S4 and has an LG G2 now, the other jflte maintainers haven't been seen for a while.
Entropy512 said:
Plans: yes
Active maintainers: not right now, jake sold his S4 and has an LG G2 now, the other jflte maintainers haven't been seen for a while.
Click to expand...
Click to collapse
Thanks for your quick reply. The other maintainers are very much involved in their own project which is based on CM and therefore is no option for me
Chartmän123 said:
Thanks for your quick reply. The other maintainers are very much involved in their own project which is based on CM and therefore is no option for me
Click to expand...
Click to collapse
I'm a few days from effectively declaring the JF devices unmaintained and shutting them off until they are.
Edit: Maintainer messaged me, they are actually alive, so nightlies will continue. Unification could be a while though.
Entropy512 said:
I'm a few days from effectively declaring the JF devices unmaintained and shutting them off until they are.
Edit: Maintainer messaged me, they are actually alive, so nightlies will continue. Unification could be a while though.
Click to expand...
Click to collapse
Thanks again I told Evisceration that there was an imminent shutdown of jflte nightlies and that he should contact you as omni is running quite stable on my (mum's) device.
Chartmän123 said:
Thanks again I told Evisceration that there was an imminent shutdown of jflte nightlies and that he should contact you as omni is running quite stable on my (mum's) device.
Click to expand...
Click to collapse
Problem was that I hadn't heard from him in ages and it seemed like he was focusing on something other than omni. But he pinged me and said he's still working on it, so nightlies will continue.
I am possibly considering a temporary shutdown until the device is unified just because it has 7 different builds right now and that's a lot of server resources, but I'm not sure. It depends on if we have another "out of disk space" or "ccache needs to grow AGAIN" incident. I plan on merging the final core prerequisite for unified device builds tonight. (specifically a patch to build/ that any device moving to unified builds needs.)
Related
Hey all
Does anyone know if MIUI is going to release a version for the GS4?
CM already told they will NOT be adding any roms for the GS4, so MIUI is my last hope..
Maybe someone made an unofficial release of MIUI-Like rom?
Thanks
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Pagnell said:
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Click to expand...
Click to collapse
Codeworkx and Faryaab are working on the i9500.
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
The Samsung devices I currently own (i9100, i9100g, i9300, i9305, t0lte, p5100) are the last ones i will officially support. Some of them might be dropped with the next big android release. Yes, i’ll NOT touch the Galaxy S 4 and whatever comes after it.
Click to expand...
Click to collapse
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Yes, things doesn't look too good for the i9500
Will Faryaab save my day? who is he?
Pagnell said:
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_samsung_i9500
So there's a chance after all :angel:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!
hackarchive said:
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!
Click to expand...
Click to collapse
Thanks for the fast reply!
Could you give me some details on what is open/working and what gives us trouble?
I assume that the sound part is difficult to get by, as they claim to have some Dirac HD licensed - given I don't know Dirac HD and their licensing policy...
aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
Do note that two former GS2 CM maintainers have this device, and we both like it.
The real key is that it's Qualcomm-based (qcom has excellent documentation), and Oppo doesn't deviate far from Qualcomm's CAF reference sources.
We also now have access to a technical contact who can answer some questions for us - many of the camera issues in CM should have been improved last weekend thanks to a tip from Oppo.
For me right now, the big question is how hard it is to get to the UART port of the device, since I think I'm going to need it for an upcoming effort.
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
SHORT VERSION: is there any stable rom for the i9305 that can also run banking apps that look at if your rooted? Or just a stable rom for i9305!? Or even a stock rom that has no bloat-ware (for i9305 of course and in uk)?
LONG:
So I started out a journey looking for a good stable rom and of course cyanogen caught my eye but I unfortunately swapped to a 4g service and swapped my phone right before embarking on this journey to a i9305 - crap!
I thought wow great 4g and 2gig ram it'll be perfect with cyanogen 11 so I waited and no M build for i9305 all year long argh! So I gave up and tried a nightly cyanogen 11 and it was buggy as hell. So gave up on that after a few weeks and trying different updates moved to carbon - again only nightly available even more bugs maybe I was just unlucky in timing but on to cyanogen 10.1 I was going backwards now not the most fun but it still has a few bugs but is way more stable and I loved the speed and camera was great but still it feels a bit old and I still prefer stock . So I am thinking now I either give up n get stock or go on to yet another one but im not confident now ...thanks!
What exactly does this have to do with the paranoid android project?
#stayparanoid
Pirateghost said:
What exactly does this have to do with the paranoid android project?
#stayparanoid
Click to expand...
Click to collapse
I suppose I was thinking paranoid was my best hope but maybe not...
Mumraa said:
I suppose I was thinking paranoid was my best hope but maybe not...
Click to expand...
Click to collapse
We don't have the manpower to take on any device requests. You need to find a Dev willing to port it. The PA team can't support your device
#stayparanoid
Pirateghost said:
We don't have the manpower to take on any device requests. You need to find a Dev willing to port it. The PA team can't support your device
#stayparanoid
Click to expand...
Click to collapse
Ok thanks never mind I thought I might of missed something on the site were a stable version for my device existed. I see now there's just not much in the way of stable roms for my device in general ...
Hi guys, anyone knows when Source Code could be released?
Thanks
The last commit of Xiaomi on Github is old of 2 years so... Will be long...
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commits/master
troufiniou said:
The last commit of Xiaomi on Github is old of 2 years so... Will be long...
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commits/master
Click to expand...
Click to collapse
Only if you look at Master branch. There are more recent commits in the device-specific branches...
Still I'm not expecting it any time soon. You can build with prebuilt-kernel, hence the current Lineage port and soon something a little different.
Yes it's hugely disappointing to not have kernel source and it does restrict some of the more fun things but at the same time it isn't MIUI and variety is always nice.
Expect something more exciting coming soon, I had some data loss and other things to deal with but now I have a little more time to spend on this.
Join the Telegram group and let me know if you want to be a tester.
The last couple of builds (haven't been Lineage) but also haven't been suitable for general release - the last lineage release already has too many bugs for daily - it will be updated soon - probably the next week.
StoneTrapper said:
Expect something more exciting coming soon, I had some data loss and other things to deal with but now I have a little more time to spend on this.
Join the Telegram group and let me know if you want to be a tester.
The last couple of builds (haven't been Lineage) but also haven't been suitable for general release - the last lineage release already has too many bugs for daily - it will be updated soon - probably the next week.
Click to expand...
Click to collapse
Thank you all for the answers, but I'm not so expert with Kernel building. I was curious to know some information about the releasing because I had a Mi5 before and after 5/6 months Xiaomi released Sources for that device
I will wait so
mryugin89 said:
Thank you all for the answers, but I'm not so expert with Kernel building. I was curious to know some information about the releasing because I had a Mi5 before and after 5/6 months Xiaomi released Sources for that device
I will wait so
Click to expand...
Click to collapse
Kernel building from scratch is a hell of a challenge without sources, even for developers hugely more experienced than me. The same kernel is compatible across a lot of devices here and there's a reason none of building it themselves. Even LineageOS where they're soon going to be adding Mi5s Plus with official support isn't using custom kernel.
I was hoping 5/6 months from release we'd have kernel but, as you know, nothing yet. Maybe 5/6 months from International release (I think Taiwan counts as international)
But using prebuilt kernel is a way to still have some custom roms. Once MIUI 9 (or 8 based on Android 7) is released that will help things a bit but in the mean time. I am working away at getting something much better than what we have at the moment.
Kernel sources have been just released!
mryugin89 said:
Kernel sources have been just released!
Click to expand...
Click to collapse
Somehow there's a gemini defconfig uploaded, rather than scorpio.
github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/scorpio-m-oss
Okay, will DL all composant on my server for making
Now the question is...
..anyone is working on Android Stock ROMs?
mega.nz/#!oBpSHQDT!b0qS_ni43rjhAK4smR2SfcMO8WXxNxkAWW4dpGWXi8c
Not from me
troufiniou said:
mega.nz/#!oBpSHQDT!b0qS_ni43rjhAK4smR2SfcMO8WXxNxkAWW4dpGWXi8c
Not from me
Click to expand...
Click to collapse
Thanks, but this is the UNOFFICIAL as we can read on xda or a testing Lineage ROM?
A build of LOS with some stuff broke
troufiniou said:
mega.nz/#!oBpSHQDT!b0qS_ni43rjhAK4smR2SfcMO8WXxNxkAWW4dpGWXi8c
Not from me
Click to expand...
Click to collapse
Which are differences between ROM you linked and this one (https://forum.xda-developers.com/mi-note-2/development/unofficial-lineage-14-1-ported-build-t3574298) ? It's not the same?