Database Info

CM has pretty poor update waiting times.

So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?

Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......

In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)

mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.

Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better

From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom

MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.

floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..

As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.

Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.

LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.

floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.

maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.

Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.

If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.

maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.

Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...

Unsafe to run marshmallows ROMs no longer supported by dev

I've been using pure white Nexus ROM for a while but the dev Trevelyan announced he would no longer be supporting it with the monthly Google security updates.
Does this mean that any phone using this custom ROM is now insecure and users should find an alternative option or just go back to stock Google ROM to ensure they continue to get the monthly security patches?
Thanks.

I guess either no one cares about security or have moved on to nougat!

Yes, no more updates means you won't be secure anymore, since vulnerabilities will be found but never fixed. Note that going back to stock won't help you, as stock also no longer gets security updates (October was the last one). You'd need to switch to a different custom ROM.

I guess I'll need to find my new daily. Looks like nougat ROMs are still iffy in terms of full functionality.

Exactly my problem. Unstable / not anymore developed roms . I'm just gonna stick to good old SlimKat..

I guess I'll stick with pure white then. If no ROMs are getting any updates from Google then they will all have the same potential security risks? At least ElementalX kernel incorporates security patches and enforces SELinux. Maybe time to buy the new pixel.... The N5 had served me well, but security is paramount for me.

There are still some custom ROMs that get security updates (e.g., CyanogenMod).

How can CM get security updates if Google has stopped providing them for the Nexus 5? I don't understand? Thanks

For a few things (the non-free vendor drivers), you're right; those pieces don't get updated. But most of Android isn't device-specific, so the community takes the updates Google pushed to AOSP for the devices they do still support and ports them to the ones they don't.

OK. What's considered best daily CM ROM?

I'd personally recommend the latest official nightly.

Seriously. Is There No Firmware That Works?

I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.

Lineage 14.1, Official. Installed the 'official way' (motorola unlock code). Not rooted. For me, working like a charm

You should try a different rom. AOSP Extended is based on AOSP-CAF. When I used a different ROM but also based on AOSP-CAF (purenexus) I faced the same problem.
Right now I’m on unofficial Lineage 15 (it still has some issues: random reboots sometimes but that seems to be an upstream issue as Pixels are also rebooting and having to use Footej camera to record video).
As @krondar said official LineageOS should be your best choice even though it doesn’t have some other more advanced custom ROM features. (Or just stock ROM from Motorola if you’re OK with Marshmallow)

Quantumstate said:
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Click to expand...
Click to collapse
AOSP Extended is one of the best you can find here. But the version you are using is very old. I would recommend you clean flash the latest version and I believe you will love it.

I tryed Cyanogenmod 13 and it was awesome, and now I'm with Lineage 14.1 and everything is ok... no bugs,

Over the years I've tried every firmware from MIUI to Paranoid Android to CarbonROM to Cyanogenmod to ResurrectionRemix, and all have one set of basic problems or another. And worse, seem to deteriorate over time!
This should never, never happen with an advanced OS in the 21st Century. So I moved to the AOSPs and find the same syndrome! This implies a basic problem with Android -- after so many years it can not be gotten right. It's alarming.
Why is Lineage better? What is it based on? How is it different that it doesn't have these problems? How do you find out that one ROM is working better than all the others?

I've been using purenexus ROM for a few month and never faced any issue,not even a little one. It was 100% stable for me and the perfect ROM for a daily driver. AEX Is very good though and lineage OS 14.1 too.

Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.

Quantumstate said:
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Click to expand...
Click to collapse
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.

Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.

V-Droid said:
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Click to expand...
Click to collapse
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.

Quantumstate said:
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Click to expand...
Click to collapse
If you don't have time to be 'bit-twiddling' on your phone then why did you bother on unlocking the boot loader and flashing a custom firmware?
Personally I haven't tried pure nexus, but it is very possible that 5 months ago pure nexus had the same bugs as AOSP Extended. Since they are custom firmwares, they are susceptible to bugs, that's why mainteiners push out weekly or monthly updates.
If you think that pure nexus or any other rom will deteriorate over time then you should probably restore the stock firmware of whatever device you are using, well... That of you have time, if not than don't blame maintainers remember they are not being paid for anything.

I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.

Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Cobvetsely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Conversely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."

I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another (hidden) unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly. Doesn't realize how silly he looks.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.

Quantumstate said:
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Click to expand...
Click to collapse
Friend we share similar views and sentiments on this subject. We also seem to share in the philosophy that The Due Process Clause, Equal Protection of the Law, and safeguards against unreasonable searches and seizures have essentially all been trampled through the mud when it comes to our privacy and expectations to privacy with respect to our smartphones. Law enforcement having the authority to compel a man (or woman) to unlock their device without constitutional safeguardsl, is synonymous of the police being permitted to kick down the door to a man's house upon a "whim" or a "hunch". Or a cop conducting a traffic stop and subsequent warrantless search of the driver's person and vehicle merely because the cop feels like it. I take great pride in knowing with 100% certainty that any law enforcement who attempts to track or trace my mobile IP, or tries to monitor anything about incoming or outbound data packets on any of my devices is chasing Casper the Ghost. But, anymore I can't be so certain about John Q Law's legal authorization (or ability) to stick his long snout into my device's internal storage. I'm working the final kinks out of a simple process that will completely wipe and heavily encrypt the wiped storage with multiple layers of random binary (with the morbidly numerous anticipation that they actually can and will spend countless man hours and resources on decrypting utterly blank and random blocks of binary jibberish). All with a self determined series of keyfob button presses.
Yeah I know I'm ranting and perhaps being a bit overzealous. But, just like you said, regardless of state or federal appellate court adjudications giving authorities such authorizations, such decisions run afoul of a handful of the most rudimentary tenets of constitutional safeguards.

Word.
Most have given up and acquiesced. But not me. Never. I use Tor to get here, and just about everywhere else. Because I know what can be done.
Most will say that their words are not important enough and so they don't worry. But they do not know that what is Ok today, may not be tomorrow. I used to be in intelligence, and most here would not believe what can happen (and has happened in other nations).
BTW, there is an excellent TV series called The Americans, which I think is as good as the old Mission Impossible series (which came way before Tom Cruise). Although it can never compete with the old Secret Agent ('Danger Man') series, and the John LeCarre series', it is a high-grade and carefully-wrought storyline.

I agree with you that seems no ROM is stable; In fact if your phone is important for you as production device, I would suggest you stick with stock ROM or keep testing until a ROM which works for you and stay there! New version introduce new bug, that's the usual case on Software side, there is no way to avoid.

If you are so sensitive to bugs then stick onto stock rom instead of blaming the developers. Your fault that you can't keep meddling with your device. If you want a totally bugles device then you try to develop a rom by yourself then you will understand what it is to be a developer

MotoJunkie01 said:
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
Click to expand...
Click to collapse
Better than my XT1540, rooted, no other mods except modified host file for ad removal, stock kernel. I have an average 1 bug report a week.

Security patches - do they have to come from the vendor?

Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?

charlatan01 said:
Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?
Click to expand...
Click to collapse
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
But before it is included in leedroid HTC has to release a new base with the patches included.
Except some special patches that are baken into custom Kernels.

diamond09 said:
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
Click to expand...
Click to collapse
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.

charlatan01 said:
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.
Click to expand...
Click to collapse
HTC includes most patches from upcoming security patches in their "older" one...like in june patch, there are patches for july etc included. that's why HTC only patches and has most of the time an older date, because they only patch necessary stuff. if they would implement everything, even the bugs from google they would have the newest date, but also a lot more to do, which is stupid, wasting time and money

Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.

Tachi91 said:
Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.
Click to expand...
Click to collapse
android Q changes those things. each phone released with android Q will have a generic system image (GSI), so they can be used straight from google, that'S why security updates will come directly from google and the OEM can update the vendor apart from it and also maybe patch the system with "modules" so you can still have htc sense, touchwiz or whatever comes with the phone

Advice needed: Most stable and usable ROM?

Howdy all! I've dug out a couple old Nexus 5's that I stopped using a while back when I got PH-1 and am looking to reflash one of them for a friend who needs a phone and can't afford to buy new. When I was using them last I was running LineageOS 14.1. I'd like to set him up with something stable that he can use as a daily driver for a while and was looking for suggestions. It looks like a ton of ROMs have been updated and I was hoping someone could point me in the right direction for a good current setup that will be easy on the battery and have the most features without compromising stability. Is there a commonly accepted "best" Nexus 5 build? I'm good at following directions, but a lot of the technical stuff is over my head, so trying to research everything I've missed for the last couple years is making my head spin lol. Any assistance would be greatly appreciated!

Stable ROM for Nexus 5
Hey,
I have found AOKP to be really good for my Nexus 5. It has the stability of Lineage 14.1, but also has a few nice little additions: OMS support for Substratum, customisable navbar, a few tweaks here and there. And it is still being developed, and receives regular updates.
Not too heavy on the fancy stuff, so for me it's a nice tradeoff between "stock" AOSP/Lineage, and a few little enhancements.
Also the Nexus 5 is officially supported by the developers, which is important to me.
I've tried Android O and Android P ROMs on my Nexus 5, but I still find Nougat ROMs seem to run the best.
I also have a Nexus 7 (2013) tablet, and the ROM is also available for that as well. As I have OCD, I "need" both my phone and tablet to run the same system, and AOKP gives me this.
Just my suggestion, anyway. Give it a try, and see what you think.
Cheers
Shaun

Thanks! I will check it out

if you like simpler thing i would suggest LOS 14.1 even tho our hammerhead are not supported officially you can use unofficial build by razorloves here https://forum.xda-developers.com/showpost.php?p=80268653&postcount=3145 or another one here https://forum.xda-developers.com/showpost.php?p=80210774&postcount=3 they updated it once a month at least with security updates each months
also if you want tor try LOS 14.1 CAF you can try this https://forum.xda-developers.com/showpost.php?p=80340013&postcount=753

I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.

petersaints said:
I also have a Nexus 5 laying around that I mostly use as an extra device to test apps on. However, since my apps usually require working Bluetooth LE and other network related stuff, I have refrained from using Android Oreo and Pie based ROMs since I always read that there's some issues with this or that.
I have stayed with the latest Lineage OS 14.1 (Android 7.1.2) and it has worked pretty well. However, I have now decided to move to something a little bit fresher, but still based on Nougat. I went with the AOKP suggestion made by @shaunoleary since they are still releasing official builds. Unfortunately the AOKP's security patch level is still on February 2019.
If want something with a more up-to-date security patch level you can also try these LineageOS 14.1 builds: https://forum.xda-developers.com/go...opment/rom-cm14-1-nexus-5-hammerhead-t3510548 which are supposed to be on September 2019 security patch level.
Click to expand...
Click to collapse
Hey Peter - thanks for the nod
I acknowledge that AOKP's security patch level is a bit dated, but having used LineageOS for a long time, I found some of the features AOKP throws into Lineage, I'm willing to sacrifice that for the extra goodies AOKP offers.
I have decided to stick to Nougat for as long as I can. I tried Oreo and Pie, and had noting but trouble with Bluetooth. It's such a shame when they bring out such a solid, stable release of Android like Nougat, and then stop supporting it because it's not "the latest".
Just as an aside, I have recently been using MicroG (Nanodroid package) instead of GAPPS on my N5 (and my N7 2013 as well), and have found it to be very usable now. Google Pay does not work, but aside from that, I get much better battery life than using GAPPS. In fact, my location accuracy seems to be better, and I've got Play Store working a treat.

Hi there, I have the same problem, my N5 stayed on last security patches from the official rom in Feb 2019. Then Lineage ended official support. Did someone try to install the unofficial version (made by razerlove) over the last official build. Would that work? Any hints?

I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------
Oh, and I dont know if it fits without the UA repartition mod, but I can attest to it working since I've modified most units with the mod at this point.
ha7msterx said:
I've tried them all it seems, having acquired dozens of units a few years back .. Im serious, i think im absurdly qualified to make this recommendation.
Hundreds of ROMs/kernels/use cases.
Maybe something is fast and beautiful, until you install more than a few apps, and then it chokes. Maybe it works great with most carriers but not the one you have. My point is that nexuses that aren't working get reformatted and a winnowing occurs.
And gradually a winner emerged. I now have this on 90% of n5s.
If you must have android 9, I recommend floko, but my #1 n5 ROM is
crdroid 7.1.2 LOS caf
with opengapps
and truesight 4.4 caf kernel ,
although the one it installs is fine.
https://forum.xda-developers.com/go...ent/rom-crdroid-release-weekend-t3182013/amp/
Click to expand...
Click to collapse