Hey all,
what is the fastest way to get security updates for the Nexus 5X? Who is faster at integrating them, Google with their stock ROMs or Cyanogenmod?
I am asking because I read that OEMs are informed by Google about one month before the security updates are rolled out. So e.g. Cyanogenmod could roll them faster than Google itself.
Anyone knows how to check when Cyanogenmod integrated security updates? E.g. for the July security upgrade, when was it rolled out by Google and when was it rolled out by Cyanogenmod?
Thanks!
Stock. Google could inform oem's but If anything appears during the curent month, google îs the first to know/care/ implement
Sent from my Nexus 5X using Tapatalk
Google. Cyanognmod is not a OEM Cyanogen inc. is and they are separate things. Cyanogenmod updates its sources after google releases the code and that happends after Nexus release. You can track the cm from cmxlog.com or cm gerrit.
Related
i'm thinking of going with aokp, but it's kinda a "turn off" for me when it comes out with a weekly build and i feel the need to constantly check on the forums and flash to a new one
what's a good one that is just solid that doesn't require a new build update every week?
You can go Aokp because the last stable build is milestone #4 all the other builds that come out are just a nightly.
Sent from my Galaxy Nexus using xda premium
Addictedtothegreenguy said:
You can go Aokp because the last stable build is milestone #4 all the other builds that come out are just a nightly.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i understand but having nightly builds makes me feel like i need to constantly upgrade to the newest one
Just... don't update then? If your setup works well just leave it. You can always skip updates.
I'd go with Bamf Paradigm. Uniquely built AOSP rom, stable, and good battery life. Try it for yourself, you'll be amazed
And quality over quantity - no hyper change logs every 4 days, but if you're in for something different, jump in.
if that is such a problem then just flash AOKP Milestones... not AOKP Nightlies + Milestones.
Milestones are for people who don't want to keep updating. These milestones come 1-2 week.
Honestly, if updating a ROM / Kernel is a "turn off" because a developer is maintaining their ROM / kernel at a rate to improve your phone more and more and you don't want to stick with that maybe you should of stayed on stock ROM/kernel? Because this is like me hearing that people are complaining about a dev updating their ROM / kernel way too much.
When you rush through things and do not test enough, you end up missing issues, which ncreases the need to update the rom more frequently.
BAMF Paradigm does not release updates like mad because for every release, we have at least 3-4 testing releases to our beta testers to find and fix bugs. We do not like to consider our users the beta testers.
I have had my HTC One X for a while after I ditched my Sony Xperia Acro S.
I currently love the phone but is it worth it to upgrade to CyanogenMod (10)?
Or should I just wait for the official JB Update.
The reason why I am asking this question is because I have heard that when you root your phone and install a custom ROM, HTC would refuse to give OTA to those certain phones that were rooted/flashed. Is this true? or can I just root/flash without worry?
Just wanted to hear some thoughts.
Foot Note:
I know the JB update isn't out yet so we can't review it and the leaked ones aren't official but I'm just curious if its worth upgrading the CM 10.
OTA is a patch, so it can't be applied to a different ROM.
If you restore your original ROM, you will be able to receive updates. If you restore original recovery, you can install the update.
BenPope said:
OTA is a patch, so it can't be applied to a different ROM.
If you restore your original ROM, you will be able to receive updates. If you restore original recovery, you can install the update.
Click to expand...
Click to collapse
Thanks for your reply. That was a typo error. I meant to say phones that were formerly rooted or flashed were not allowed to receive OTAs anymore for the stock rom but anyway, thank you.
Ooshi said:
I currently love the phone but is it worth it to upgrade to CyanogenMod (10)?
Or should I just wait for the official JB Update
Click to expand...
Click to collapse
Depends really just on you. But if you are unlocked already. You can try it out and revert back as Ben said.
If you hate Sense as me, and like CM, CM10 can be your choice.
I have only few issues with CM10 but wont switch back to Stock despite them.
The issues I am still facing is:
1. flickering, despite different kernels, stock rom has this figured out better
2. WiFi also stock ROM much better, on CM it wont switch in my network to a better AP no matter what I do....
But thats about it it has many benefits for me. Some of them, that come to top of my head.
1. DPI Change to 240 and I wont have tweak the notification bar (also it has the nice color change on connect to google + percentage)
2. Updates, I love nightlies
3. Fast but so fast... no unnecessary crap
4. Multitasking much better as on Stock where its non existing
I love CM/AOKP (and all the builds based upon), but due to HTC's laziness and closed nature, the 'best & latest' drivers for the One X will always be with Sense. That is in respect to the latest kernel, camera framework, beats & audio drivers. Yeah sure HTC release their kernel sources eventually, but usually by the time they have a new kernel from them is out. I dread to think about when the community will get the 3.1 sources.
The camera is the biggest loss for me, the Sense camera, especially with the JB camera build is just far better than any CM/AOKP camera or Play Store app I've tried. To even come close we really need someone to take the camera out of CM/AOKP (or create a new app) and modify/update it solely for the One X.
When running Sense I really miss proper density settings (Sense crashes on density lower than 300), and with most ROMs I have to spend time de-bloating.
With all the hardware issues I've had with my One X at the start, HTC's retarded bootloader warranty policy, and other general unhappiness, I'm going with a Google phone next time - Best community support and openness. 3rd parties seem to only care about pushing their own software, most of which is just bad compared to AOSP. Then don't get me started on contract branded handsets, I don't know how people on here can handle getting updates soo late.
I prefer cyanogenmod ben it is true that SENSE bring many interesting feature ! :good:
I like the AOSP/CM10 look of Android, but there are issues that annoyed me and forced me to go back to sense roms. Flickering, Wifi, Battery and the most important one was Camera.
Now usually I get a sense rom and de-sense it.
Ooshi said:
Thanks for your reply. That was a typo error. I meant to say phones that were formerly rooted or flashed were not allowed to receive OTAs anymore for the stock rom but anyway, thank you.
Click to expand...
Click to collapse
HTC Wouldn't do that! They provided the ways to get root, so in a sort of way they support it.
Cyan Delta App
As an aside, if you switch to Cyanogenmod 10 you can use the Cyan Delta app from the Play Store. This is brilliant if you like the nightlies as it only downloads the actual changes and not the full rom.
This app really makes life easy if you like flashing a rom daily. Saves repeatedly loading all your apps and settings, etc.
Just a thought!!
Regarding your question, I was going to wait for the official OTA Jelly Bean update, but got sick of waiting. For what it's worth, my highest benchmark on Antutu with CM10 is 12686 though when you go to submit it says 12706. (I'm unsure why Antutu gives you one score then adds a bit on?). Highest score on ICS stock Rom 12486 preliminary and 12518 final.
Cheers,
Dave
Hi,I just have a few questions I would like to ask
1. Is there any battery drain?I know the factory 4.2 rom has it , but how about PARANOIDANDROID?
2. In 2.54,there's a "cm colour" option under advance settings , is that option still available in 2.99?
Thanks
The battery drain is going to be there on 4.2 depending on how you have your Google services set up regardless of rom.
As to #2, it is now aosp based, and some cm tweaks are being merged in. It may or may not make it in. Right now their focus is on working toward the stable release.
Remember, 2.99 is beta, and although very usable as a daily driver, isn't quite what the devs feel is suitable as a final product. If stability and optimal battery are paramount, you might want to refrain from flashing beta software. Conversely, if you want to live on the bleeding edge and are willing to live with a bit of instability, betas are a good peek at what you might be able to expect in the upcoming stable release.
Sent from my Nexus 7 using Tapatalk 2
Thanks for the prompt reply,I think there is a misunderstanding here.
Where I said "cm colour" , I meant the colour profile which PA 2.54 came with.Now I know that PA 2.99 has a new kernel, I just want to ask if that particular profile is still there.
Is there anyone who had tried PA 2.99 knows whether there is a significant battery drain?
Thanks again though.
Its not just a new kernel. The rom is built from an entirely new base. It was previously based on cyanogenmod 10, but is now using soap as a base. As such, its not going to have many of the cm tweaks that were present in 2.54 and earlier. Some, but not all, may eventually make their way into the stable release, which will be PA 3.0.
As for battery drain, yes. Its essentially a given with 4.2. If you check battery stats, Google services are the generally the culprit.
As I've said PA 2.99 is beta software, and various bugs should be expected.
Sent from my Nexus 7 using Tapatalk 2
Haven't experienced any battery drain, but i agree it would depend on your user settings, etc.
Sent from my Galaxy Nexus using xda app-developers app
I got bored and decided to build from the master branch of AOSP. This branch has the latest code changes and fixes however its not a release branch so some things may be broken too. I haven't touched any of the code the only thing I added was root. You will need to add Google Apps if you choose to use them. Also you will need to wipe if you're coming from another rom. I will keep this updated if enough people use this, if not consider this experimental.
Today's Download: http://d-h.st/4Ge
Cool, another openmaster user.
Sent from my Nexus 10 using xda app-developers app
tried out open master but there was some small things that I did not know how to fix that caused me to go back to release branches
I've learned a lot more since I posted this project which has been abandoned
Did you build user or user debug?
Sent from my Nexus 4 @1.5 GHz on Stock 4.2.1
I thought the whole idea of beta release updates was tk provide 2 things Testing, fixing bugs and glitches and also to allow developers time to fine tune apps for compatibility with the upcoming stable releasing.
Yet here we are Goodlock which is Samsung & Synergy OneUI Theme Compiler......all still not compatible with A10
You would think that logically they would have had everything ready.
Samsung especially since they knew when A10 was releasing. Pretty Bad Management.
Lol
Darkat70 said:
I thought the whole idea of beta release updates was tk provide 2 things Testing, fixing bugs and glitches and also to allow developers time to fine tune apps for compatibility with the upcoming stable releasing.
Yet here we are Goodlock which is Samsung & Synergy OneUI Theme Compiler......all still not compatible with A10
You would think that logically they would have had everything ready.
Samsung especially since they knew when A10 was releasing. Pretty Bad Management.
Click to expand...
Click to collapse
Yeah, testing, fixing bugs, and glitches with Android 10 on the device, not on supplementary apps.
Way back when i had the Nexus 6P . Google mentioned that one of the reasons why betas are released is for developers to ready their apps.
Good Lock took months to update fully last year for Pie as well on the S9 series. Keep in mind also, they are likely seperate dev teams, and there was a much shorter beta this time around, so the Good Lock team likely didn't have enough time. The base app, and a few plug-ins work.
As for a 3rd party app, that's a whole different scenario. You'd have to ask them why it doesn't work.