i read something in the net while i was surfing yesterday, you can look here: http://www.androidcentral.com/motorola-atrix-hd-gets-official-cyanogenmod-support
and then reading these lines made me surprised(maybe getting official cyanogenmod support for ancora is impossible after this moment but who kowns?)
If an Android device has enough of a following, and there are developer(s) willing to commit (no pun intended) to maintaining the device in the official CyanogenMod source tree, this device becomes officially supported -- and receives official builds of the CyanogenMod ROM.
if someone be maintainer for our device can we get official support from CyanogenMod?
is this really possible?
ı mean our device source code are available in github(kernel source device source and vendor files)
maybe forking our device source into CyanogenMod source tree can make this possible or am ı wrong??
maybe this is a bulsh*it after this moment but just wondering
for example galaxy s is getting official support from Cyanogenmod still if im not mistaken mr. pawit is their maintainer and developer
ım waiting your answers brothers what do you think about that? @arco68 @arsradu @LeroViten @honeyx and all ancora devs
with my best regards :good:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
honeyx said:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
Click to expand...
Click to collapse
ı understood bro but is there any hope for galaxy w? return of ancora :good: and also ı understood that from your comment : technically this is possible,galaxy w can get official support from CM Team but this is unnecessary for this dead device isnt it?
I simply don´t think this will happen because you have to look from their point of view.
1. this device is a low activity device in Amercian terms. 2. So never was that popular to get their attention. 3. is already old and not up to date. 4. It´s hype time is almost over and many earlier SGW users are going to replace it. 5. CM is going a different route now and will be focusing on their "device" they are going to launch soon. And finally 6. Why should they change this now after already 3 years?
So if I were CM I would look for the future not looking back to the past with it´s outdated devices and not even waste a single tought about devices like the SGW.
Is this bad for the SGW owners? As long we are having Devs like Radu who are porting the latest ROMs to this device it really doesn´t matter CM is supporting it officially or not supporting it.
So what do you expect from being supported by CM? You only would be able to install the latest nightlys launched by the CM team with all the bugs in the CM code included and maybe some day fixed. A Dev who is porting their CM sources of course has to fight with these bugs too, but also cares to fix the most important ones.
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
SGWUser said:
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
auhh thats true sir arne is right as always anyway thanx man for informing us
regards :good:
I don't think so...anyway, we already have the stable n smooth ROM so far. Without Officail, it's does not matter at all.
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
hack4er said:
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
Click to expand...
Click to collapse
That would be so f... Awesome *-*
Please we need someone who knows how to do this
Related
Hye all,
i just open this thread to attract attention of any developers that may can maintain or compile a new type of AOSP - OMNI rom
Here the following forum for this OMNI rom
http://forum.xda-developers.com/forumdisplay.php?f=2601
Developers can submit theirs device specification to OMNI development forum > http://forum.xda-developers.com/forumdisplay.php?f=2604
it is nice to had fresh ROM to be compiled or been maintain for our wonder.. i had no knowledge in compiling ROM and i hope somebody could try make it real..
Maybe our sir @arsradu can take give a chance
Here some video that presenting this OMNI Rom
www.youtube.com/watch?v=BXlzJ4WVDKY
Thank You For reading
Wow the room looks great from the video , I hope that someone will support it for Wonder
Sadly I would need a hardware upgrade for that... I actually needed that for a very long time and didn't get the finances to do it and I can't seem to get any support from anyone else so far...so I can't make any promises for this ROM. It looks nice and it might turn out to be a great ROM but I won't make any promises about implementing it for Ancora because of the reasons mentioned above. If anyone else wants to do it, be my guest.
maybe we could gather some workgroup on that? but we need some people that had experience in changing the config.. it same goes with me, building a rom need high hardware requirement..if not it will took long time to build it..
dear sir @arco68
sir can you merge ancora device spesific into omni github please?
http://forum.xda-developers.com/showthread.php?t=2483720
http://forum.xda-developers.com/showthread.php?t=2483593
ı know you are very busy sir but ı want so much official omni rom and support for galaxy w
also there isnt any official rom(cm paranoid slimbean etc.) for galaxy w
maybe this will be first who knows??
than you very much sir for your huge work on our device :good:
best regards
hack4er said:
dear sir @arco68
sir can you merge ancora device spesific into omni github please?
http://forum.xda-developers.com/showthread.php?t=2483720
http://forum.xda-developers.com/showthread.php?t=2483593
ı know you are very busy sir but ı want so much official omni rom and support for galaxy w
also there isnt any official rom(cm paranoid slimbean etc.) for galaxy w
maybe this will be first who knows??
than you very much sir for your huge work on our device :good:
best regards
Click to expand...
Click to collapse
There is dude. LiquidSmooth was official. AOIP was official. But there wont be many because this is a minority phone for mainstream developers. We must truly thank the devs like educk to even have spent so much time for us to make LS and Carbon. Not to mention the dual boot kernel.
Sent from my MB860 using Tapatalk 2
hack4er said:
dear sir @arco68
sir can you merge ancora device spesific into omni github please?
http://forum.xda-developers.com/showthread.php?t=2483720
http://forum.xda-developers.com/showthread.php?t=2483593
ı know you are very busy sir but ı want so much official omni rom and support for galaxy w
also there isnt any official rom(cm paranoid slimbean etc.) for galaxy w
maybe this will be first who knows??
than you very much sir for your huge work on our device :good:
best regards
Click to expand...
Click to collapse
Would be so awesome to get official OMNI Rom support
is there any good news about omni @hadidjapri?
sorry if ı disturb you
thanx again
with my best regards :good:
I hear, hadidjapri working on it
Any news about Omnirom for our wonder
ı think we have chance for official omni support because we are using legacy camera libs and we need that changes in framework/native
http://review.cyanogenmod.org/#/c/34376/
luckily omni merged that commit into their framework/native repo 3 month ago
https://github.com/omnirom/android_frameworks_native/commit/6233f1e7dcdc087fd4e4aaf4d8626ad5303fb9c8
also we have official twrp recovery for omni(omni requires twrp recovery configuration for porting) http://docs.omnirom.org/Porting_Omni_To_Your_Device
http://forum.xda-developers.com/showthread.php?t=2046035
firstly we must build as unofficial and then we must merge our device,vendor and kernel tree into official omni git repository http://forum.xda-developers.com/showthread.php?t=2483720
we only need dev or devs for maintaining
@Madridii and @hadidjapri bro you are experienced for that jobs maybe you can work together and you can be our official manitainer fo official omni support
thanx
regards
sir mordred said:
ı think we have chance for official omni support because we are using legacy camera libs and we need that changes in framework/native
http://review.cyanogenmod.org/#/c/34376/
luckily omni merged that commit into their framework/native repo 3 month ago
https://github.com/omnirom/android_frameworks_native/commit/6233f1e7dcdc087fd4e4aaf4d8626ad5303fb9c8
also we have official twrp recovery for omni(omni requires twrp recovery configuration for porting) http://docs.omnirom.org/Porting_Omni_To_Your_Device
http://forum.xda-developers.com/showthread.php?t=2046035
firstly we must build as unofficial and then we must merge our device,vendor and kernel tree into official omni git repository http://forum.xda-developers.com/showthread.php?t=2483720
we only need dev or devs for maintaining
@Madridii and @hadidjapri bro you are experienced for that jobs maybe you can work together and you can be our official manitainer fo official omni support
thanx
regards
Click to expand...
Click to collapse
Hello!
Also We need this commit too in frameworks/native :
MemoryHeapBase
before that I am not a developer as I said before so sorry , we are just trying with hadi, arsradu and all of my friends to keep this phone up to date with CM and google updates(example : DarkCM is CM11 with more option to make it different), I think there is someone who tried to build it but it didnt boot!
and in my case, I am so busy with University, If I have a free time I will discuss with my friends.
Hello guys
As Marvellous team doesn't have our phone as primary,and Jdevs team is not active right now,we need to wake up our phone and make a complete team.
Any joiners for now?
And add this to your signature for everyone to see
add this text to your signature
AmirNajjar said:
Hello guys
As Marvellous team doesn't have our phone as primary,and Jdevs team is not active right now,we need to wake up our phone and make a complete team.
Any joiners for now?
And add this to your signature for everyone to see
add this text to your signature
Click to expand...
Click to collapse
I've been on the WFS forums for more than 2 years now, and in that time I've seen 2-3 teams been made and then disbanded due to a change in the developer's primary device..............Plus the fact that this device is over 2 years old and an ARMv6 one bring limitations to future development
I seriously do not think another team would do any good to the development.........Also I'd like to add the Jdevs' team is active on their new ROM, it takes a lot of time to do things they have planned for the next release. This actually is like the standstill modpunk gave us between some CM9/CM10 releases
So please be a little patient about it
csoulr666 said:
I've been on the WFS forums for more than 2 years now, and in that time I've seen 2-3 teams been made and then disbanded due to a change in the developer's primary device..............Plus the fact that this device is over 2 years old and an ARMv6 one bring limitations to future development
I seriously do not think another team would do any good to the development.........Also I'd like to add the Jdevs' team is active on their new ROM, it takes a lot of time to do things they have planned for the next release. This actually is like the standstill modpunk gave us between some CM9/CM10 releases
So please be a little patient about it
Click to expand...
Click to collapse
I understand but we must make a team for our poor device,and we can,even if my primary device isn't WFS,I'll still work on it
AmirNajjar said:
I understand but we must make a team for our poor device,and we can,even if my primary device isn't WFS,I'll still work on it
Click to expand...
Click to collapse
The Marvellous Team is less active for the WFS because nearly everybody changed of device, and because I - the only one who still has only a WFS - have started new studies and must work a lot. But we still work on cm10.2, and still support our ROMs. @Kevinjoa is very active, @thehacka1 too, Kevinjoa updated AOSPA and still has the best cm10.1 rom out there, thehacka1 made AOSP 4.0 and updated PAC-man v23 ^^
But starting a new team is a good idea Even if, as @csoulr666 says, it maybe won't speed up development a lot.
Anyway, which roms do you plan to make ?
New ROM project
izi501 said:
The Marvellous Team is less active for the WFS because nearly everybody changed of device, and because I - the only one who still has only a WFS - have started new studies and must work a lot. But we still work on cm10.2, and still support our ROMs. @Kevinjoa is very active, @thehacka1 too, Kevinjoa updated AOSPA and still has the best cm10.1 rom out there, thehacka1 made AOSP 4.0 and updated PAC-man v23 ^^
But starting a new team is a good idea Even if, as @csoulr666 says, it maybe won't speed up development a lot.
Anyway, which roms do you plan to make ?
Click to expand...
Click to collapse
I am using @Kevinjoa's CM10 as build and make it "Kit-Kat Look-And-Feel",I will add OTA updater to the ROM ,and I will make it have features from many ROMs
AmirNajjar said:
I am using @Kevinjoa's CM10 as build and make it "Kit-Kat Look-And-Feel",I will add OTA updater to the ROM ,and I will make it have features from many ROMs
Click to expand...
Click to collapse
Good idea
izi501 said:
Good idea
Click to expand...
Click to collapse
I still need help
I want to add more wallpapers
so I am decompiling CMWallpapers.apk but the problem is the id so it replaces the old one
and when changing the id the apk breaks
any help???
Why you try to decompile apk ? CM is opensource you know bro. HERE is source and you can fork repo add changes and compile with eclipse.
i think this method easier than yours.
hi guys, we've got 5.1.1 officially but cm13, based on android 6.0, is even sweeter (doze, app permission control, etc) . did you hear any news from devs?
It looks like that Temasek and Joshndroid are already preparing an unofficial CM 13 Build for our SM-P600 Tablet.
Look at https: //github.com/temasek/android_packages_apps_Settings/commits/cm-13.0
&
https: //github.com/Joshndroid/device_samsung_lt03wifi/tree/cm-13.0-test-rebasecm12
I can tell you that the p600 will get official CM13 if @joshndroid, @ Shawn, and myself can figure out why we get a black screen after rebooting from recovery.
Sent from my SM-P600 using Tapatalk
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
joshndroid said:
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
Click to expand...
Click to collapse
How is the status? Any progress?
Stogie87 said:
How is the status? Any progress?
Click to expand...
Click to collapse
i am getting succesful builds but am getting black screen (back light turns on but nothing shows). unsure whether its kernel or vendor related or even tree related with something not activated? looking at some other device trees to see what they have changed
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Stogie87 said:
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Click to expand...
Click to collapse
best to work on the base cm rom first before working on derivatives. I will be releasing a temasek rom for cm-13.0. But we need cm-13.0 working first. More hands on a single distro makes hopefully better/lighter work. Once we get a cm happening, all the derivatives will come next so everyone wins.
Hey guys its devut again informing you that HOX's Device tree is nearlyready!!!
UPDATE: DEVICE TREE IS NOW COMPLETE
Nearly
Yes Nearly because libdgv1 is still taking time
libdgv1
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
Here it states that we get a lot of problem because
Code:
dlopen()
is a POSIX COMPLAINT:crying::crying:
So here it is nearly perfect Marshmallow device tree
https://github.com/DevUt/android_device_htc_endeavoru/tree/Marshmallow-begins-part-1
I also have not tested it for new layout
If you are a developer then please check it
[ Do not go for storage_list.xml (as it is deleted , go for fsatb)]
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
DevUt said:
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
Click to expand...
Click to collapse
*finger crossed*
bopung said:
*finger crossed*
Click to expand...
Click to collapse
I think it will take alot of time cause it is verrryyyy confusing
Added issue section in my github repo
1 issue added
you guys also help me by telling me the issues in code
Should i add wiki to my repo to guide other developer?
Or should leave them on their own to figure out how to make libnvos and other thing works ( cause just looking at the tree you wont be able to understand because the patches are also in proprietary files )?
And another great news the device tree wil be ready till Monday!! :laugh: :good: ????????????
Device tree complete now no monday
DevUt said:
And another great news the device tree wil be ready till Monday!! :laugh: :good:
Click to expand...
Click to collapse
(After this many ppl)
Critic : Monday ? What! You are so slow DevUt!
DevUt : Sorry , Thats the way im!
DevUt : But for other HOX DEVS
DEVICE TREE IS NOW COMPLETE
NOW NO MONDAY
DEV GET THEIR HANDS ON!
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
MaRtYy01 said:
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
Click to expand...
Click to collapse
My pleasure dude
I predict you will see mm till mid may cause my net is slow
Thanks for Patience and all your support
But if you wanna try to make a rom from this tree you can (please check the issue section if there are none then please proceed to building if there is even 1 Stop ; I will fix it )
Guys i just found out that we need to have a newer version of twrp to flash marshmallow on our hox. So here's my thought
First i will Fix the device tree ( yes i will be adding some more. Patch files which are on my local pc)
Then as we already have the kernel available for marshmallow.
And then i will build the new twrp and it all in a post
Guys fact of the matter : HOX doesn't runs well on newer roms! And yes thats the bitter truth for every Phone once its old it losses its powet
But why
Here's a logical answer : It is in the way the developer makes the newer roms!
What !
Yes ! Actually the devs just patch some existing files and add some new ones and release it !
And i dont blame the devs for it cause nobody will waste his/her time in writing everything from kernel , Device tree ,proprietary files they sum upto millions and millions of files
Thats causes the problem.
So whats the solution
The solution is nothing! But as a HOX lover i would love to take this whole summer for HOX
So whats your plan
My plan is after releasing marshmallow i would work to write the whole thing scratch (not exactly scratch) but i will make it the most stable rom for HOX
I know im making many promises but believe me i would make them true :highfive:
Thank you for your work, I'm looking forward to marshmallows for HOX.
I'm out of the station for 10 days will come and back to work ASAP
Is this a rom?
sagor1 said:
Is this a rom?
Click to expand...
Click to collapse
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Guys bad news my laptop screen has disturbed it is showing vertical lines I will send to soon for repairs and continue until then see my github progress ! You have surprise in both the kernel and my own profile
DevUt said:
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Click to expand...
Click to collapse
With sense or without sense?
sagor1 said:
With sense or without sense?
Click to expand...
Click to collapse
Without, its based on cm13
Sent from my Nexus 7 using XDA-Developers mobile app
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.