As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Gokulbalram said:
As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Click to expand...
Click to collapse
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
iKillCypher said:
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
Click to expand...
Click to collapse
What do you guys hate Exynos for? Kernel Sources?
Gokulbalram said:
What do you guys hate Exynos for? Kernel Sources?
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
chasmodo said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Click to expand...
Click to collapse
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Gokulbalram said:
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Click to expand...
Click to collapse
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Entropy512 said:
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Click to expand...
Click to collapse
There's only one source for a MediaTek chipset, the one in Android One. At least MediaTek is getting better, they're taking steps.
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
ahmedelhofy said:
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Gokulbalram said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Click to expand...
Click to collapse
Yea, I know I already said that I won't be sad to see it getting dropped..
Last week, jakew02 said that he's going to drop support for Galaxy S4 LTE (jflte) when Lollipop arrived. He's leaving the source up, but OmniROM Lollipop on the S4 will need a new maintainer.
The key message here is that the core team can't maintain every device!
As much as we hate to remove devices, there will be a significant number removed, if there's no active maintainer for it. No device will be enabled for L nightlies (and thus official support) if there's nobody active and competent who is maintaining it.
If you've always wanted to get involved, now really is the time - L is upon us, and good things are happening
Going forward, if there is sufficient interest from the community (i.e. go out there and talk to devs and contributors from other projects please!), we are more than happy to facilitate making the 4.4 branch of Omni an ongoing project.
For this to work though, it would require enough developers to come together on legacy devices to make it viable. With new major Android versions, a lot of custom ROMs simply don't continue support for devices "left behind", but we're willing to try this out as an experiment. If there are sufficient (experienced) developers, we'll have 4.4 as an active project which will accept features and patches as normal.
For this to work though, it does require everyone to play their part - we'll need reliable people to review and approve changes etc, as well as active maintainers for devices.
aidfarh said:
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Click to expand...
Click to collapse
Hi,
that's not really necessary if you ask me. We could always bring the kernel in sync with CAF, but that's it. This is also what OEMs do when updating their kernels (apart from fixes and such). Jerpelea, a Sony Mobile developer, agrees (see this post).
Also there aren't many "active" Xperia fusion3 (Z, ZL, Tablet Z) maintainers at the moment , and I haven't had enough time for such things.
BUT: Contributions are always welcome.
Help
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Hunter1998 said:
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Click to expand...
Click to collapse
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
I became one overnight ._. (Nowhere near a skilled maintainer though.) I only know how to compile. Nothing other than that :/
lg e450
sorry if this the wrong thread to post.
I have an old lg e450(mtk 6575), and all the sources has been released by lg. Can anything be done to make this device alive?
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
Who do I need to contact to help?
Related
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
nicholaschw said:
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
Click to expand...
Click to collapse
Again?? Aren't you tired? You went over it but people from the forum certainly not. I absolutely don't wanna argue with you but yesterday Jarred aka Universal SS droped the ARM thread and today you are back.And you are not the same person. Certainly not. You are like bad news,they never fail.
nicholaschw said:
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
Click to expand...
Click to collapse
Good for you. Hope it works out better this time and test thoroughly before release and after changes.
might is a understatement. It almost certainly will cause bugs to appear (the most common bug is it not booting when major changes are made to the kernel base). Also allot of the bugs from the kernel don't show symtoms they just go wrong and use a few more KB of memory or that bit restarts and causes a slight slowdown or it takes a few milliseconds longer to complete its task etc.
Edvin73 said:
Again?? Aren't you tired? You went over it but people from the forum certainly not. I absolutely don't wanna argue with you but yesterday Jarred aka Universal SS droped the ARM thread and today you are back.And you are not the same person. Certainly not. You are like bad news,they never fail.
Click to expand...
Click to collapse
Your comments (although highly entertaining) don't do much, at least he's trying. Your right though: some information is contradictory.
EDIT: Have a taco
xonar_ said:
Good for you. Hope it works out better this time and test thoroughly before release and after changes.
might is a understatement. It almost certainly will cause bugs to appear (the most common bug is it not booting when major changes are made to the kernel base). Also allot of the bugs from the kernel don't show symtoms they just go wrong and use a few more KB of memory or that bit restarts and causes a slight slowdown or it takes a few milliseconds longer to complete its task etc.
Your comments (although highly entertaining) don't do much, at least he's trying. Your right though: some information is contradictory.
EDIT: Have a taco
Click to expand...
Click to collapse
I don't get it
First it was Nicholas who said he's handing it to a new maintainer, who is Jared, right? And Jared mentioned it has been dropped support
http://forum.xda-developers.com/showthread.php?t=2034227&page=10
Good news for everyone!ARM. will drop support for the LG optimus black!Hope everyone is happy and have a nice day.(I'll still be in the forums though)Moderators please lock this thread
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
And now ARM Project's back?
Yes. He is fed up of this community. So, he turned over to support HTC. I give him my support for DNA. Now, i comeback to finish off what is destroyed, complete whats junk, and make it into something like a useful book into a library. Thanks xonar. I still have one last lesson. I did not learn drivers. edv, as said above, thats my motive. And, the reason why i comeback is the value of my life. You rather change an enemy into a friend rather than gaining more opposition.
nicholas for f--k sake !!! , once you have the kernel going post the topic and flatter yourself ,, you never learn do you
If this is going to turn into a flame war then I'll close it as that's not needed here but as it's posted in General, you should be here to discuss the topic. It's been explained why the other one was dropped but if nicholaschw wants to try develop something out of it let him and just ignore this thread if you don't have anything productive to add to it. This wasn't posted in Development so he's not expected to have the kernel ready to post so discussion is allowed here.
Thanks
AvRS
ARM Project TEAM.
To get away our doubt to you, may I ask you something about your ARM Project?
You have many thread there,
Optimus Black
Optimus 2X
Xperia Arc
HTC Droid DNA
Samsung Galaxy S3; and
Google Nexus 4.
And I got this post,
nicholaschw said:
We are an non-profit organisation alike cyanogenmod, but only focusing on creating a global aftermarket kernel for the Android OS, specifically to remove the major setbacks of linux.
Click to expand...
Click to collapse
So you're involved with (kind of) non-profit organization (alike CyanogenMod), can we know who's the members of your team? AFAIK, you don't own the phone in personal. So you (might) develop those kernel alone by yourself, or how many developers in your team?
I read your ARM. Project Recruitment, and it seems no one interested, so this non-profit organization doesn't existed yet, or you already have your own internal team?
redy2006 said:
To get away our doubt to you, may I ask you something about your ARM Project?
You have many thread there,
Optimus Black
Optimus 2X
Xperia Arc
HTC Droid DNA
Samsung Galaxy S3; and
Google Nexus 4.
And I got this post,
So you're involved with (kind of) non-profit organization (alike CyanogenMod), can we know who's the members of your team? AFAIK, you don't own the phone in personal. So you (might) develop those kernel alone by yourself, or how many developers in your team?
I read your ARM. Project Recruitment, and it seems no one interested, so this non-profit organization doesn't existed yet, or you already have your own internal team?
Click to expand...
Click to collapse
We currently are five-membered. Xperia is full, me, jared and pidozz. Two more are under evaluation. See ARM.'s git
Good Luck with whatever you're doing, I hope you learn someday.
My better half made me a delicious taco and while eating I read the comments.
It was not my intent to flame, neither argue with anyone. I will rather get drunk and party till morning. Good year everyone.
Sent from my LG-P970 using xda premium
Edvin73 said:
My better half made me a delicious taco and while eating I read the comments.
It was not my intent to flame, neither argue with anyone. I will rather get drunk and party till morning. Good year everyone.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Off topic but good year to you too,here they don't serve tacos
Sent from my LG-P970 using xda premium
hmm, 80% of repos are forked from already good kernels from such devs like gokhanmoral, CM, garwedgess, coolya, etc.
it's like forking Diana kernel then adding a little touch.
Even your "bproj repo" is a clone from huexxx https://github.com/ARMP/bproj-black/blob/master/Makefile#L198 yet you pushed it as initial commit. I understand, maybe you're shy to fork it repo to repo.
Your Makefile on the repo shows:
export KBUILD_BUILDHOST := $(SUBARCH)
#ARCH ?= $(SUBARCH)
ARCH ?= arm
#CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
CROSS_COMPILE ?= /home/huexxx/android/arm-2010q1/bin/arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Lol. He gets owned pretty much doesnt he?
In the Nexus 4 forums he told us that he works for google btw.
realfelix said:
Lol. He gets owned pretty much doesnt he?
In the Nexus 4 forums he told us that he works for google btw.
Click to expand...
Click to collapse
if i am, i would be in the newspapers. I'm so young. And go look at the post. FATHER. One more thing, this post is useless as gab himself is more capable to give this community a kernel
Thread closed as per OP request.
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Maybe because there are too many new phones in this interval of time and our s3 mini is not the most popular
Sent from my Motorola Startac
joshtk98 said:
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Click to expand...
Click to collapse
The main problem seems to be that the ST-Ericsson Novathor sources are not available.
I think that devs are focusing on more powerful devices like the s3 or s4, bigger guns are always better, aren't they?
Sent from my GT-I8190 using xda app-developers app
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
vtetuan said:
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
Click to expand...
Click to collapse
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42730302&postcount=25
The guy only wants to learn. And I'm not saying that you have no reason.
It's the classical fragmentation in Linux community, and now, in Android community.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Scuppa said:
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Click to expand...
Click to collapse
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
New Macław said:
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
Click to expand...
Click to collapse
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Paul L. said:
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Click to expand...
Click to collapse
I don't need access to your machine, I would like to keep releases on my own hand, but of course I can help you
Poke me at gtalk please: [email protected]
Hi Guys,
i am wondering that there is absolute no AOSP Development for the Z3+/Z4 aka "E6553". I would love to do it by myself but i dont have a Computer which would be able to deal with Compiling and so on. I think hundreds of Users would be very happy and thankful if someone would start Developing for our Device. The really strange thing is the Z5 and the Z3+/Z4 are 98% the same device, same Hardware except of the Fingerprint Sensor and the resolution of the Camera, even the Build Source from Sony is the same for both devices, there is AOSP Development for the Z5 but the Developer dont even answer to questions for other Devices. I for myself would love to Support if someone´s starting with development, with testing or a little donation.
Regards
Trilliard said:
Hi Guys,
i am wondering that there is absolute no AOSP Development for the Z3+/Z4 aka "E6553". I would love to do it by myself but i dont have a Computer which would be able to deal with Compiling and so on. I think hundreds of Users would be very happy and thankful if someone would start Developing for our Device. The really strange thing is the Z5 and the Z3+/Z4 are 98% the same device, same Hardware except of the Fingerprint Sensor and the resolution of the Camera, even the Build Source from Sony is the same for both devices, there is AOSP Development for the Z5 but the Developer dont even answer to questions for other Devices. I for myself would love to Support if someone´s starting with development, with testing or a little donation.
Regards
Click to expand...
Click to collapse
You don't request development
You MAKE development
Kizoky said:
You don't request development
You MAKE development
Click to expand...
Click to collapse
There are dozends of requests in the cross device development section.
I think you had better complain to jerpelea, his FXP team hasn't built ROM for a long time.
UPDATE: found it, they didn't upload on androidfilehost. http://uploaded.net/f/53n94q
RyTekk said:
I think you had better complain to jerpelea, his FXP team hasn't built ROM for a long time.
UPDATE: found it, they didn't upload on androidfilehost. http://uploaded.net/f/53n94q
Click to expand...
Click to collapse
Really Big Thanks!
Could you tell me Who made this and perhaps a link to a thread or a webpage of the developer?
Trilliard said:
Really Big Thanks!
Could you tell me Who made this and perhaps a link to a thread or a webpage of the developer?
Click to expand...
Click to collapse
fxpblog.co
FXP team maintains them, jerpelea is team leader as well as leader of Sony Program Development.
Trilliard said:
Hi Guys,
i am wondering that there is absolute no AOSP Development for the Z3+/Z4 aka "E6553". I would love to do it by myself but i dont have a Computer which would be able to deal with Compiling and so on. I think hundreds of Users would be very happy and thankful if someone would start Developing for our Device. The really strange thing is the Z5 and the Z3+/Z4 are 98% the same device, same Hardware except of the Fingerprint Sensor and the resolution of the Camera, even the Build Source from Sony is the same for both devices, there is AOSP Development for the Z5 but the Developer dont even answer to questions for other Devices. I for myself would love to Support if someone´s starting with development, with testing or a little donation.
Regards
Click to expand...
Click to collapse
Is there any way that people can help with the compiling and stuff? cuz ide be happy to help you with alot of computing power
It was a good ride...
https://www.cyanogenmod.org/blog/a-fork-in-the-road
Yep.. All nightlies will be discontinued.. Too bad CM
LineageOS
The link in the word Lineage take us to a GitHub for a new thing called LineageOS. So if I'm guessing what the future holds correctly, CM is getting rebranded as Lineage?
I look forward to the new direction. But I won't be using it until camera on OP3 is as good as stock.
Sent from my ONEPLUS A3003 using Tapatalk
Nooooooo! Please tell me this is an early April Fools joke.
RIP CM
Welcome LineageOS
https://github.com/LineageOS/android_device_oneplus_oneplus3
Yeah that's bad news man! But somehow it will live on we all know that. Thanks 4 the journey
I've used CM since 2.3.3. Thank You CM. Looking forward to the future...
Been using CyanogenMod since v6 on my Motorola Droid until now to v13 on OP3.
Was glad to see CM grow & was really amazing but now it's gone. RIP CM.
XDA loves you and Welcome LineageOS 2017.
Happy Holidays to all, Hope 2017 brings us a new Dawn.
Bring on Lineage.
While it is true that Cyanogen mod will loose it's name, the legacy behind the name will live on. Steve Kondik still owns the rights to his code, just not the name and as you have seen, everything is getting moved over to it's new home under the name of LineageOS. Screw Cygyn, they took CM into a completely different direction of what Kondik envisioned and to tell ya the truth, I am glad this happened, to get the OS back to it's roots and the meaning of what Kondik intended it to be from it's birth. Back to being for the community, by the community, giving the best experience, functionality and customizations for our devices, not about a bunch of corporate bs, greed and money.
kenboyles72 said:
While it is true that Cyanogen mod will loose it's name, the legacy behind the name will live on. Steve Kondik still owns the rights to his code, just not the name and as you have seen, everything is getting moved over to it's new home under the name of LineageOS. Screw Cygyn, they took CM into a completely different direction of what Kondik envisioned and to tell ya the truth, I am glad this happened, to get the OS back to it's roots and the meaning of what Kondik intended it to be from it's birth. Back to being for the community, by the community, giving the best experience, functionality and customizations for our devices, not about a bunch of corporate bs, greed and money.
Click to expand...
Click to collapse
Totally agree, I'm glad this is happening to, CM in its present form just uses too much bandaid and patch works solutions for its many bugs. I miss the CM back in the day. Hopefully lineage will bring that experience that Kondik originally envisioned back.
2016 can't leave normally.... Oh my god R.I.P CyanogenMod if it's true.
_MartyMan_ said:
2016 can't leave normally.... Oh my god R.I.P CyanogenMod if it's true.
Click to expand...
Click to collapse
It's True
Hope that future LineageOS will support OP3 also
GamaX320 said:
Hope that future LineageOS will support OP3 also
Click to expand...
Click to collapse
ALL current devices that have CM support, WILL have LineageOS support. lineageos is the same code a cm, they only had to change the name for legal reasons, as cyanogen inc. owns the cyanogen mod name.
They're importing the code to the github now. Give them a couple more days for nightlies to roll out.
bencozzy said:
Cyanogen is actually looking to bring legal action against the devs trying to rebrand CM as lineage OS so I wouldn't get too excited. It will be more excited to see CM die completely so we can have some real development occur or at least see some OEMS pick up the good developer's out there.
Click to expand...
Click to collapse
I don't know why you think that CM death would give benefit to the whole Android development scene.
It's not like there is lack of good developers in the world available for OEMs and open source ROMs, so her we are: a good established open source project shut OFF and pursued by Cyanogen Inc., and not much good alternatives available.
What is left?
AOSPA? No Nougat release.
Omni? Lights and shadows.
Other interesting custom ROMs not CM based?
bencozzy said:
Cyanogen is actually looking to bring legal action against the devs trying to rebrand CM as lineage OS so I wouldn't get too excited. It will be more excited to see CM die completely so we can have some real development occur or at least see some OEMS pick up the good developer's out there.
Click to expand...
Click to collapse
Without CM or Lineage, there's not much hope for dedicated development for many devices. Even today many devs rely on CM kernel to build newer version of android and wait for CM devs to fix bugs first and then cherry pick them.
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Same feeling here..!
Yes,.. well said,
Need support for Official TWRP. need adb sideload feature.
Please developers and maintainers, consider lineage 16.0 and omni rom, these two are major famous os distro, but not maintained for our device.
All the points are true and devs should at least try to fix the recovery. I remember once my old device had a problem with Cwm when reboot to recovery was performed the phone bootlooped so a stable recovery is a basic need for development.
Also now a days devs seem to make telegram groups and post their work there by giving reason that xda has a lot of rules, the rules are for everyone's good and if you find a rule which should be changed or modified ask the community they'll help.
On xda devs get to show their skills in front of an open audience instead of a closed group. It's like driving on a empty track vs driving in a formula league. The league has more rules than no rules empty track but one can outshine only in a league.
So try to support the xda community and also have great time. Happy developing.
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
Very thoughtful! Resonate the same things brother.
Most annoying - 'Bugs - you tell me' when they are crawling around about to eat your eyes out!!
Oh and the spammers - next level entitlement for free stuff.
Note - Same as OP and with all due to respect to devs/contributors.
Can we request the developer community to focus on quality and not on quantity, found more than 20 roms, but not one which can maybe support OTA and be used as a daily driver for non flashoholic community?
Ie flash once (or dirty flash forever) and forget type of use cases, we had during resurrection remix days.
Other than that I completely agree with the opening comment of the thread.
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
Due to the insane quantity we find similar bugs on different roms, that's kinda futile..
Not one is working on lineage 16 i absolutely don't understand why.
I just bought a new ZF MPM1 and roaming around the forms ,i feel like you are absolutely right!
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
saurabh1234 said:
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
Click to expand...
Click to collapse
first of all i thank my dear X00TD's ROM developers for the quick and active development.,
Bro,
we are not pesking developers to add this thing and that thing. we are requesting necessary thing that needed for stable development. every month we are getting new rom project or port rom. but nothing is different.
I am custom rom user since samsung galaxy pop( galaxy mini). previously every community build the cwm recovery (project closed) and make it stable and make it compatible with all the roms. and parallely start developing CyanogenMod (now lineage). then otherr rom developers are uses cyanogenmods sources to build their own custom rom.
firstly,
stable recovery needed. our twrp is still in beta stage.
and still in unofficial release. the following problems i faced, adb sideload, otg support not stable, aroma also not working.
secondly,
lineage os is traditional one and best aftermarket os. and the root for the many custom roms. but we are not concentrating on this os.
nxp amplifier not yet fully supported for current release of pie custom roms. i dont know what is the problem behind this issue. but none of the thread mentioned about it. may be asus not released source for it(idk).
anyone can build rom and fix bugs and release here. sorry to say, most of us don't know this android custom rom development.
and telegram groups are not worth. mostly some guys talking off topics. and i mostly ignore if unread msg is more than 500( mostly it goes above 1000 per day). so i miss what developers told and published news.
anyone,
please make a thread to how to take a logs, because most of us dont know how to take logs.
please make a index thread for list roms and kernel and about their present bugs, last release, current development status.
please make a single thread for noob guide/new user, and mention all the common problems and its solutions,
please make a thread for common bugs in roms and kernels and talk there for what we need to do solve this bugs.
if possible, update possible reason for the bugs
sorry i dont know english much. ya i know did more grammer mistakes.
i'm really sorry if i hurt anyone.
#OnlyRequesting
#NotDemanding
What else can you expect? Phone has been marketed as a mid-to lower middle tier device (price <$200/€180) i.e. it will not attract big (known / reputed) devs. phone was released in few countries so lower economic tier ppl in these countries will flock to this phone....natural to expect slovenly behaviour, rude attitudes in the community and lack of stability and direction of growth for the phone's rom development, since these ppl (students, mostly) have little knowledge of ethics, professionalism, and are likely to throw the device away for the next shiny fondleslab in the same price range within a year. Some devs are there, but the general populace they pander to is reckless, raging, mercurial youth with little respect for their work and little concern/care for whom they offend, so they can't stick to these guidelines as you speak of....after all they too hold some other work/profession as their main job and rom development is just an after-work thing....
Eat whats on table coz you aint paying ****.
I agree with what you said.
I've been longing for a stable Pie LineageOS or stable AOSP for months. But so far it's been no news.
well, it can't be helped
My actual plan was to just use the stock rom (since it was pure aosp, kinda), but since the pie version still buggy I have to use the custom version, which is pretty meh than my previous devices (xiaomi)