Lollipop
No doubt the big news at the beginning of November was the release of the Android 5.0 Lollipop source code. AOSP began seeing the code on the 3rd, and completed the majority of the push on the 4th, with some remaining stragglers seeing code uploaded midday on the 12th. Work on CM12 began in earnest at the end of last week, and you can now successfully sync and build the work in progress against a handful of devices.
We are unlikely to enable nightlies against CM12 until towards the end of this month, or early next month, as we work to incorporate the CM features you’ve all come to appreciate into the new code base, and reimagine those that no longer translate to the Material look of L. It is also currently too soon to tell how many devices will transition from 11 to 12, though early traction has this number higher than we had initially hypothesized.
Home builders and community members are welcome to take a peek at the builds at their leisure, just repo init the new branch using the following command:
repo init -u https://github.com/CyanogenMod/android -b cm-12.0
Again, please be aware that not every device is in a ‘daily driver’ state under CM12, and the codebase is nowhere near feature complete. Our contributors are working hard, and our gerrit is aflutter with activity. If all goes well, we’ll have something special to welcome the upcoming holidays and New Year.
Happy Flashing
-The CyanogenMod Team
ps: can someone finaly tell me why the hack are there s3 QandA threads in here???? s3 has their own section for A and Q -.-, why do the spam here in i9305 forum???
klemen241 said:
Lollipop
No doubt the big news at the beginning of November was the release of the Android 5.0 Lollipop source code. AOSP began seeing the code on the 3rd, and completed the majority of the push on the 4th, with some remaining stragglers seeing code uploaded midday on the 12th. Work on CM12 began in earnest at the end of last week, and you can now successfully sync and build the work in progress against a handful of devices.
We are unlikely to enable nightlies against CM12 until towards the end of this month, or early next month, as we work to incorporate the CM features you’ve all come to appreciate into the new code base, and reimagine those that no longer translate to the Material look of L. It is also currently too soon to tell how many devices will transition from 11 to 12, though early traction has this number higher than we had initially hypothesized.
Home builders and community members are welcome to take a peek at the builds at their leisure, just repo init the new branch using the following command:
repo init -u https://github.com/CyanogenMod/android -b cm-12.0
Again, please be aware that not every device is in a ‘daily driver’ state under CM12, and the codebase is nowhere near feature complete. Our contributors are working hard, and our gerrit is aflutter with activity. If all goes well, we’ll have something special to welcome the upcoming holidays and New Year.
Happy Flashing
-The CyanogenMod Team
ps: can someone finaly tell me why the hack are there s3 QandA threads in here???? s3 has their own section for A and Q -.-, why do the spam here in i9305 forum???
Click to expand...
Click to collapse
I tried to build Lollipop myself but i get some annoying error. BTW s3 threads in the s3 lte Q/A are heck of a spammers.
limnaln said:
I tried to build Lollipop myself but i get some annoying error. BTW s3 threads in the s3 lte Q/A are heck of a spammers.
Click to expand...
Click to collapse
my friend ported aosp to lg l9, the phone i used to own. But i guess its easy from nexus 4 to lg l9, i kinda hate samsung for the complexity of porting
klemen241 said:
my friend ported aosp to lg l9, the phone i used to own. But i guess its easy from nexus 4 to lg l9, i kinda hate samsung for the complexity of porting
Click to expand...
Click to collapse
I didn't tried with AOSP, I tried with CM12.
Hi guys, it's true that s3 will not receive official cyanogen mod cm12 ? It's not even showed on github branchs about this device. https://github.com/CyanogenMod/android_device_samsung_i9300/tree/cm-11.0
I'm on a group about cyanogen mod on facebook, an italian group, and there a guy from this group that said me that s3 will not be supported from cm12, no lollipop officially speaking from cyanogen mod, only unofficial. So it's really true ? Someone here know something about this story ?
Related
Not trying to be a troll - I'm looking for some insight.
It appears to me that there is a degree of inefficiency with the progress of the Camera updates being made on the HP TouchPad. Those updates are on a static and aged build of CM9.
What does it take to have the code/ROM updates for the working camera ported over to the more recent builds of CM9 and CM10?
I know the inside joke/anti-troll repellant response of "two weeks" or "soon" are out there. That's not what I'm looking for. I'm really trying to understand why devs would continue to leave these advancements off of the more recent/enhanced builds?
Is the answer really just that the single dev (or team) wants a static version to perfect the driver so it doesn't have to keep "changing the wheel on a moving car"?
--McBean
McBeanTIO said:
Not trying to be a troll - I'm looking for some insight.
It appears to me that there is a degree of inefficiency with the progress of the Camera updates being made on the HP TouchPad. Those updates are on a static and aged build of CM9.
What does it take to have the code/ROM updates for the working camera ported over to the more recent builds of CM9 and CM10?
I know the inside joke/anti-troll repellant response of "two weeks" or "soon" are out there. That's not what I'm looking for. I'm really trying to understand why devs would continue to leave these advancements off of the more recent/enhanced builds?
Is the answer really just that the single dev (or team) wants a static version to perfect the driver so it doesn't have to keep "changing the wheel on a moving car"?
--McBean
Click to expand...
Click to collapse
Dorregaray explained it in a RootzWiki post: http://rootzwiki.com/topic/16347-de...hw-acceleration-fix/page__st__170#entry965452. I think changes have been made to upstream CM9 that make inclusion of the camera fixes more complicated.
bananagranola said:
Dorregaray explained it in a RootzWiki post: http://rootzwiki.com/topic/16347-de...hw-acceleration-fix/page__st__170#entry965452. I think changes have been made to upstream CM9 that make inclusion of the camera fixes more complicated.
Click to expand...
Click to collapse
the new code for the camera is simply not commited to the CM9 repo at the moment. It is awaiting approval by someone who can review the code. However, it is possible to "Cherry Pick" the code updates into a new build. I was doing exactly that this morning, with some difficulty, and did not end up with a better product than what is currently available, ie. blue screen on boot sometimes...
-SGA- said:
the new code for the camera is simply not commited to the CM9 repo at the moment. It is awaiting approval by someone who can review the code. However, it is possible to "Cherry Pick" the code updates into a new build. I was doing exactly that this morning, with some difficulty, and did not end up with a better product than what is currently available, ie. blue screen on boot sometimes...
Click to expand...
Click to collapse
Ooh. Good to know. I had thought that there were changes that needed to be made to existing CM before the camera stuff would be compatible with it. The fact that it's all ready to go is excellent news!
bananagranola said:
Ooh. Good to know. I had thought that there were changes that needed to be made to existing CM before the camera stuff would be compatible with it. The fact that it's all ready to go is excellent news!
Click to expand...
Click to collapse
Yes, it seems like most of the fixes that needed to be made for the memory split have been implemented in theory. However, I imagine the blue screen issue would need to be solved before the code is merged into CM9, as it makes it less than stable. Be it as it might, I think we would still do fine with unofficial CM9 camera builds if the code is never merged at all.
Hello
I'm reading a lot of comment about people never buying a SAMSUNG phone again on this forum.
I believe it has something to do with CM team ( who are these guys? ) and the CPU type and source code.
Could you please care to elaborate? As I am planning on upgrading to GN2 but ofc I need root access and the latest OS all the time
Thank you.
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Dmwitz said:
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Click to expand...
Click to collapse
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
I guess it all depends whether or not you want to run CM custom roms on your device.
Furthermore Samsung promised to release the Exynos sources...So we'll just wait and see
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
It's not impossible to bring new roms without sourcecode - we still have CM10 and will get CM10.1 - but the experience is not the best, and devs have to put A LOT of work to even make it work.
Samsung promised they will release their sources - yet untill today - they didn't. So it's simple as that, if they release sources - devs might finally fix some bugs and push CM10 into stable. Without sources we might never go out of nigthlies because some bugs might never get fixed.
As for SONY, yes they release all their sources, but remember that they used to be like Samsung untill their market share shrinked, so now they're most likely just trying to appeal to customers with that. Hope they won't change their mind about it when/if their sales go high again ( I'm looking at you Xperia Yuga )
User_99 said:
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
Click to expand...
Click to collapse
Very true, but I think they don't give a ....about a few devs and users being frustrated when they sell millions of devices...Like most of the big selling companys
bebseh said:
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
Click to expand...
Click to collapse
I think u r talking abt this thread..especially this one..
a pall of gloom has descended on the community it seems
check out CM 10 thread
i hope its a temporary phase -
http://forum.xda-developers.com/showpost.php?p=35210934&postcount=1651
Samsung didnt want the devs to work for the android community because in the end it gives an advantage to google and its os. Samsung wants people to buy its phones because of their new features added in their TW that are not available on true android. They in the future wants their devices ti be free from the android pool. Because of the tiring update process. No source code release is just what keeps dev from moding their devices so they can market their new phones and limit those features in the old models. I dont think they will care about dev going to other vendors. Because once they got hold of a new indigenous OS. they will market its dev kits and hardware for developers and they know how to bring them back.
Sent from my GT-N7000 using xda app-developers app
Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
SecUpwN said:
Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
Click to expand...
Click to collapse
A few of us are interested in this and we'll see what can be done
BytecodeMe said:
A few of us are interested in this and we'll see what can be done
Click to expand...
Click to collapse
Awesome! What are you planning to do?
SecUpwN said:
Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
Click to expand...
Click to collapse
Even if every vulnerability fix was included in source, (for now) it will still not be secured. Unless you compile your own builds with a different platform key, your builds will not be secure. This applies to nearly every AOSP-based custom ROM.
We've talked about it, and we might implement something for milestone releases. But security is a huge huge problem to take on with custom ROMs and there are a lot of heads to the dragon to take down
Sent from my HTC One using Tapatalk
Romanbb said:
We've talked about it, and we might implement something for milestone releases. But security is a huge huge problem to take on with custom ROMs and there are a lot of heads to the dragon to take down.
Click to expand...
Click to collapse
True point. But I'm sure that folks who can add unicorn sparkles to a ROM will even discover and implement some really cool security enhancements & fixes for the already known vulnerabilities. After all, this is a suggestion and to be seen without pressure. Waiting for your next awesome release for M7UL, @Romanbb! You're doing a great job!
SecUpwN said:
True point. But I'm sure that folks who can add unicorn sparkles to a ROM will even discover and implement some really cool security enhancements & fixes for vulnerabilities. After all, this is a suggestion and to be seen without pressure. Waiting for your next awesome release for M7UL, @Romanbb!
Click to expand...
Click to collapse
For sure. I'm definitely not against security enhancements by any measure.
Why isn't it possible to create a tool that can repackage ROMs with custom keys, say, using a Windows computer or Xposed Framework?
Also, isn't Mempodroid what allows us to give apps SU permission?
pan.droid said:
Also, isn't Mempodroid what allows us to give apps SU permission?
Click to expand...
Click to collapse
No. Mempodroid is an EXPLOIT and a vulnerability, please don't mistaken it with SuperSU.
SecUpwN said:
please don't mistaken it with SuperSU.
Click to expand...
Click to collapse
Okay. Just so long as you don't *mistake* 'SU' with SuperSU=)
AOKP Kitkat Rom
The Android Open Kang Project (AOKP) team has released nightly builds for a number of Android running device which bring Android 4.4.2 KitKat update for these devices. One such build is also available for Sony Xperia Z, which runs Android 4.3 Jelly Bean.
gteknet said:
The Android Open Kang Project (AOKP) team has released nightly builds for a number of Android running device which bring Android 4.4.2 KitKat update for these devices.
Click to expand...
Click to collapse
As you might have guessed, AOKP runs through all my veins. I'd probebly never use anything else, if not forced to. As soon as a new nightly is out, I'm using it. But what exactly is the AOKP team doing to make their build more secure?
One of the features that I'd LOVE to have would be encrypted calls between AOKP builds without having to be online or installing additional software. Would such be possible somehow?
Thread cleaned
I suggest several members use the ignore user option if they want to remain members on XDA
I will be keeping an eye on posting. Cut out the infantile crap or you will be removed
This is a development site, take your garbage to a social media site
Senior Moderator
@kennyglass123, thanks for cleaning it up. I really appreciate your effort. Unfortunately though, no member of the AOKP team has answered my initial question yet. Could someone please do so?
SecUpwN said:
As you might have guessed, AOKP runs through all my veins. I'd probebly never use anything else, if not forced to. As soon as a new nightly is out, I'm using it. But what exactly is the AOKP team doing to make their build more secure?
Click to expand...
Click to collapse
Sadly, this question is still open. Since I'm using M7 (Gerneric GSM), maybe @Whitehawkx can answer this?
As of every hour and every minute now we seeing new ROMs popping up for various devices now and but seems that the development for our ghost has come to end??
Well something requested by us is simply rejected by the senior members with all due respect.
For example:I recently demanded for a stock like Marshmallow based rom coming with all the special moto features like display,voice,etc.. but they rejected and recommended to try the cm 13 which loses all the Moto functionalities!?
Hence I finally put a request for one more time to build special type of ROMs for our moto devices just like the XOSP(Xperia open source project) and honourable name it as "MBOSP"(MotoBlur Open Source Project).
As much as i would love to have such rom, Moto X is 3 years a old device and I don't think anyone will work this much for an older device. I am using official CM13 by @Megatron007 and it is great. Maybe you should request the devs of existing roms to add Moto functionalities in their roms.
There can't be a Marshmallow stock rom, because there isn't a Marshmallow stock rom to start with.
There can be if built from aosp
LOL no
There can be atleast a stock like!
At this point I just want to have my verizon 1060 bootloader unlocked. I got it after it had been updated with no chance of putting cyanogen on it
I demand a working Nougat rom right now!
Those damn developers should do something to earn those salaries paid by XDA.
minimum a donation xD by users
"For example:I recently demanded for a stock like Marshmallow based rom..."
What are you paying?
Hello. There is no custom rom for samsung s23 (sm-911b / ds)?
No, and sadly, there will unlikely ever be.
It looks like you are new to XDA, actually you should only add the "Development" tag if you are actually posting your own development, questions and discussions like this should have the "Question" tag.
Lol ... Very curious to know what come to the conclusion "and sadly, there will unlikely ever be".
The phone has been released 3 months ago, stop staying misinformation.
There is already one for the S23 ultra.
tobiasmargit77 said:
Hello. There is no custom rom for samsung s23 (sm-911b/ds)?
Click to expand...
Click to collapse
[ROM] BeyondROM v1.2 [16/05/2023]-[AWD1]-[SM-S91xB]
Latest Version v1.2 [16/05/2023] ROM Maintainer: Andrei @starbucks2010 ROM Info: Supported devices: S23 Ultra SM-S918B & S23 S911B ROM Base: S91xBXXU1AWD1 (Android 13 OneUI 5.1) May2023 Patch Level ROM Features: Kernel: Stock Samsung...
forum.xda-developers.com
gaara19 said:
Lol ... Very curious to know what come to the conclusion "and sadly, there will unlikely ever be".
The phone has been released 3 months ago, stop staying misinformation.
There is already one for the S23 ultra.
Click to expand...
Click to collapse
Yeah it's not certain a custom rom will never be released, but the software currently being released by OEMs (and especially Samsung IMO) is already so jam packed with features and quite well executed as well.
I once used to root every android phone I had and even flashed new roms daily as I was doing beta testing. Ever since my Pixel 5 however, this desire has been gone completely. And it appears this is the same for other users, as the user activity on XDA is only a fraction of what it used to be in the days when I was still here for Samsung Nexus S and Galaxy S4 roms.
Me Gusta said:
Yeah it's not certain a custom rom will never be released, but the software currently being released by OEMs (and especially Samsung IMO) is already so jam packed with features and quite well executed as well.
I once used to root every android phone I had and even flashed new roms daily as I was doing beta testing. Ever since my Pixel 5 however, this desire has been gone completely. And it appears this is the same for other users, as the user activity on XDA is only a fraction of what it used to be in the days when I was still here for Samsung Nexus S and Galaxy S4 roms.
Click to expand...
Click to collapse
It's really a community thing. I agree users tend to not using custom ROM anymore. And yes, it's coming mostly because Android is just becoming as almost perfect and Samsung is really doing a great job with OneUi & update on time.
But I believe users tend also to keep the same smartphone longer than before. So I guess , and if the community is still there, custom ROM could have a big place once Samsung will stop to do major update on the S23 (in four years approximately).
So let's see, this phone is awesome, and could have the perfect hardware to make it alive longer than 4 years.
The future will tell
If some people work on bringing up LineageOS on this phone please let us know. People are already working on the OnePlus 11 and Moto X40, with non-booting builds for now.
We need to join forces to bring AOSP/LineageOS to the sm8550. CAF sources are available, Samsung sources too, bootloaders can be unlocked, so there's no reason we can't achieve this.
dekefake said:
If some people work on bringing up LineageOS on this phone please let us know. People are already working on the OnePlus 11 and Moto X40, with non-booting builds for now.
We need to join forces to bring AOSP/LineageOS to the sm8550. CAF sources are available, Samsung sources too, bootloaders can be unlocked, so there's no reason we can't achieve this.
Click to expand...
Click to collapse
yess samsung release their source code, but sometimes they left few broken code that couldn't be track down easily because of no version control system.
faizauthar12 said:
yess samsung release their source code, but sometimes they left few broken code that couldn't be track down easily because of no version control system.
Click to expand...
Click to collapse
Yeah I know that unfortunately, but there's still CAF sources