Related
You know.. it's kind of crazy the captivate is as old as it is, and roms are still being produced (at a fairly large rate) for this device.
For some time now, it has become increasingly apparent XDA could use a slight overhaul or at least a new implementation for the end-users.
I would like to see a review system that allows you to browse by device, then shows you the android roms available based on which version you want to use. .....4.1, 4.0, 2.x......
From there, it could be broken down by most recent version vs. previous versions.
It could have different criteria for review such as battery life, lag problems, how "polished" it is, how well "featured" it is.
Maybe, even an optional set of code for any devs who want to include it which standardize some automatic reporting features so there could be "official XDA stats" and then "subjective user stats"
The reason I'm suggesting this is because even the Captivate which is now *old* by any standard has ample roms for it many of which change at a fast rate. If there was a system that let you see what the original problems were, when they were fixed, and what new problems people were having, it would make the process of rom selection a bit easier. Especially since users have drastically different needs from user to user, and different developers often have different priorities.
We could even have a "voting" system or something where if a user loads up CM10 and feel it has sufficient stutter, A user can go check the "current issues" related to that nightly and click "me too!" so that other users can get an idea of how many people are having what issues. This would also allow us to mark which version of a particular rom we are on and it could even have a system which "moves us" if we report going to a new version/go back device to device.
This would be particularly useful for people who want to give feedback about roms/help developers but, don't want to keep reporting already well known issues vainly, as it would prevent having to look back through 20 forum pages or 15 days of change-log to see what is what. It would also keep users from switching to a new rom, hoping it doesn't have X problem and finding out it does.. only to have to go back and recheck and see if they need to report that issue as well.
XDA is all about the developers but, it's important to consider that a lot of us don't mind giving input/helping/beta-ing and using roms and we even decide our next devices based on what things look like here. That is a 500$ purchase some of us make judging by the atmosphere here at XDA. It is a decision that in a lot of ways pays off, we get to use newer versions of android long after manufacturers quit caring.
If I don't care that the front camera is broken, in CM10 nightly X67 and doesn't work for me, but it works for another user.. Then this can be documented in a much easier to read, easier to follow fashion which would save someone else a lot of time if they don't want to gamble on an unstable camera since they scan lots of QR codes. Especially if the camera was in fact working for almost everyone in the nightly before.
Snow_fox said:
You know.. it's kind of crazy the captivate is as old as it is, and roms are still being produced (at a fairly large rate) for this device.
For some time now, it has become increasingly apparent XDA could use a slight overhaul or at least a new implementation for the end-users.
I would like to see a review system that allows you to browse by device, then shows you the android roms available based on which version you want to use. .....4.1, 4.0, 2.x......
From there, it could be broken down by most recent version vs. previous versions.
Click to expand...
Click to collapse
I don't know how the rating system you spoke of would really work out because just as a problem with a ROM could be caused by an error in the code or build, the same problem could be caused by end-user error and any ratings based on that could cause problems with getting an accurate rating.
However what I very much agree with is your idea to break down the listings by software versions. At least if that was implemented within the Development section it would make navigating so much more efficient.
m1batt1 said:
I don't know how the rating system you spoke of would really work out because just as a problem with a ROM could be caused by an error in the code or build, the same problem could be caused by end-user error and any ratings based on that could cause problems with getting an accurate rating.
However what I very much agree with is your idea to break down the listings by software versions. At least if that was implemented within the Development section it would make navigating so much more efficient.
Click to expand...
Click to collapse
While I do understand your point about it possibly being end-user related, the reason I don't consider this too big of an issue is because there is always a chance for end-user screw ups with any product.
And being totally honest even if it is end user related, it would allow tracking of possible problems people create for themselves.I do my absolute best to read the instructions two or three times and get everything nailed down before I flash a new rom but, I've made mistakes and said "oops" on more than time.
If we can add that much more clarity to end user created problems vs. inherent rom problems, seems like that much more reason to go through with it.
If I can go back and see X is a problem from Y. I would know, "oh I forgot to clear my cache!" go back, repeat the process do it right and wouldn't have to complain to the dev.
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...
Wow. Just wow. I mean, this phone has got to be at least nine months old by now. And guess what - I haven't seen a stable build of CM11 yet. In fact, I haven't seen a build where audio even works as it should, and in the latest nightly, the audio derped out completely, even in calls. GPS doesn't work. WiFi drops every 5 minutes or so. Mobile data doesn't activate for about half an hour, even then it drops out every 5 minutes, just like the WiFi.
Cyanogenmod is beyond a joke. The Moto G runs stock android out of the box, so there is literally nothing for the CM team to modify to get CM to work on it. They should at least get audio and GPS working - in contrast there is an unstable, unofficial build for the Samsung Galaxy Ace "s5830" of CM11 that has more things working than the current "official", "stable" build on the Moto G.
I thought CM was meant to be about bringing Stock android to all devices, on Google's schedule, long after OEMs and carriers have dropped support for these devices. What's crazy here is that the Moto G's "stock" software has had a version of 4.4.4 available for months; Motorola have finished it, and carriers have got round to rolling it out - and it's been on my phone for several weeks now.
My point is, Motorola (who are very lazy when it comes to updates) have finished 4.4.4, given the update to carriers, who then procrastinated about rolling it out for weeks before finally rolling it out, and still, despite all this, Cyanogenmod haven't even got a stable build of kitkat at all, let alone 4.4.4, to offer. They are literally worse than OEMs and carriers at updating their phones on time.
If you have a Moto G, please do not ruin it by installing cyanogenmod on it. It is useless beyond belief, and you will cry for days about having turned your phone into an expensive paperweight. On the bright side, if that corner of your piece of paper just won't stick down, go ahead and install CM.
Is this is a complain or something like that lol? BTW I don't have any issues with CM or CM based ROMs.
Here we go. At this point, I am also waiting for a more stable version of CM 11 for Falcon. Yes, there are issues with it. Some are pretty notable, others are barely (or not at all) notable.
The thing here is that you are using open sourced software. There are some really, really experienced developers working on CM 11 to make it better for us, the end users. However, and I have seen this happen before, some lesser-experienced developers might forget about something every once in a while causing issues on the devices. This can happen. It happens to everyone, Motorola developers included (just look at the reports of battery drain issues across the Android versions).
CyanogenMod is a great team and are introducing features that improve Android in small, yet very useful ways. These features, in themselves, are working brilliantly. The only quirk with this is that CyanogenMod is trying to get each and every different phone to run Android in combination with those features. I might be wrong here, but that seems like that's causing a lot of trouble over some different devices, including the Moto G. If CyanogenMod adds a new feature to (for recent issues' sake) audio for devices CyanogenMod support (an update library for example), there's always a chance that gets pushed to the Moto G, and there's something with the Moto G that makes it not function properly. This is really notable in the Nightly releases. The most recent Nightly releases, 07-24 and 07-25 contain an issue that makes it so that audio isn't functioning properly. This is always a possibility. It's a Nightly, unstable, release. You cannot complain that it's not working on a version that's not intended to be stable.
This brings me to another point, the "Stable" release category. Moto G's most recent "Stable" release, M6, is really pretty stable. On everyday use, I could not see any one issue with it. The reason for there not being a M7 or M8 "Stable" release, is that there's issues with them, so CyanogenMod decided that it shouldn't be classed "Stable" for our device and therefor did not release them. I'm sure that, when there's a new safe-to-be-called-Stable release, CyanogenMod will push that to our device as well.
CyanogenMod is open source. There are bugs in it. You sign up for that in exchange for some new features and continued support from the developers. For the most part, the core software is stable. It's the "drivers" for the phone that are causing issues. Also, the new features have to be tested and the bugs that are in them should get reported to CyanogenMod so that the team can fix them. If you don't report the bugs, how would they get squashed? I have reported the audio issue on the most recent Nightly releases to CyanogenMod, which brings it to their attention and, while it is being fixed, the Nightly releases are temporarily postponed until the issue is fixed to prevent any further harm that this issue might cause. That is what CyanogenMod is about. They release something, obtain feedback, fix it, release that fix, obtain feedback, fix it and release that fix. That cycle keeps continuing. If they don't obtain feedback, they will just keep doing what they are doing -- add new features, which might cause the bugs you found to keep being there forever and ever.
And you may say that trying to report stuff in Nightly releases isn't 'allowed' on their feedback site, you're looking in the wrong place. You should look in the Nightly Regressions section of the CyanogenMod JIRA -- not the regular Issues section.
If you have any comment on what I just stated, please do reply to me. If there's anything that's wrong with what I just stated, please do correct me. If you dislike anything about what I just stated, please do not just post a hate comment on it -- actually explain what you don't like and why so I can, in turn, respond to that as well.
Thanks for reading.
I've never had problems with CM11 i'm using xt1032 btw
Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.
I've just heard they've stopped development for the Moto G entirely. Motorola and the various carriers their phones are on have got their act together and released 4.4.4, CM haven't finished... ...anything.
moto_g_n00b said:
Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.
Click to expand...
Click to collapse
Whoa… No need to swear. I'm not flaming on you. I even partially agree with you. I just provided you with what I think about the matter, and nothing negative about any of what you commented. There's absolutely no need to go crazy about what a few members comment on your post.
Have a great day, sir, and lighten up a bit.
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.
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
#reserved 1
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
TiTiB said:
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
Click to expand...
Click to collapse
Thanks for the info about the S5e, i was unaware of how well it is supported.
I would definitely do stuff like fingerprint, widevine, Bluetooth (PEN) and stuff.
But idk about those keyboards samsung offers and how they function since i cant test it on my own.
Same goes for the LTE but im pretty sure i can just use the same blobs.
BTW anyone has a firehose package for the tab s6 by chance???
I too would love LOS in this device. Samsung UI is cluttery, lagging (on mine), and an absolute mess. My PocoF1 gives me better Honkai Impact 3 (a gatcha action fighting game) performance than this tablet, and the poco is an SD845, with lite LOS. So yeah, I'd love to have this. My warranty is void anyways (because samsung decided so I haven't done a thing to void it), so it'd be great to have a reason to take advantage of that.
Chiming in for a plea to get a Lineage build for the Tab S6.
Such a gorgeous piece of hardware beset by such a ****ty software implementation. Why does Samsung insist on abusing its customers? I'd gladly pay for a Lineage or AOSP rom for our device.
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Thargorsson said:
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Click to expand...
Click to collapse
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
ykkfive said:
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
Click to expand...
Click to collapse
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Thargorsson said:
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Click to expand...
Click to collapse
oh...
there were some cpu/voltage tweaks for the same cpu before for my old devices. and for our tab s 6 there are a few devices with the same cpu like one plus. you can search the cpu model in github and then you can find the code name of it and those devices which use the same cpu. i used to get those tweaks for modifying kernels for my previous devices. however for our 855, sadly there's no port for the samsung devices afaik, so you may need to make some more changes in order to port them
---------- Post added at 05:54 ---------- Previous post was at 05:35 ----------
just found this one https://github.com/kdrag0n/proton_bluecross/releases
it should be a 855 with some oc according to the change log, but unfortunately i couldnt load the changes with my browser so i couldnt find the relevant commits
may be you can take a look at that
Thargorsson said:
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
Click to expand...
Click to collapse
I'm in at 17.1 level and up. Don't want to go back...
YES! Yes please please please! I have been dreaming and hoping LOS would come to the Tab S6 for SO long now. So yes, please make a rom for it. Please.
I would love to have LOS rom support on the Tab S6! The lack of Lineage OS support was the one thing holding me back from purchasing the Tab S6, compared to the Tab S5E, but I wanted the faster processor, storage, and larger memory capacity.
That said, if you develop a working LOS rom, that would be a huge win for all Tab S6 users!
I don't think there is a person on XDA with the tab S6 that would not want to see a custom lineage Rom built. I do want a working Spen though. Im on stock 10 One UI 2.5 and samsung is extremely slow at releasing the kernel source code for the 860. Its definitely worth it to use to build one if you can. Thanks for developing on the tab S6.
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Still On The Fence.
lucgardos said:
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Click to expand...
Click to collapse
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
DeanoD said:
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
Click to expand...
Click to collapse
Well if your not rooted you dont need odin you can install official release update. If you mean to install custom rom like lineage you again dont need odin after you install TWRP.
Actually, on debloated rooted stock ROM I don't see any problems so far..Device is holding it solid and sound.
Flavour of Lineage is absolutely welcome, but personaly I wouldn't use it because a lot of bugs and non functional addons.
Personally...this tablet without pen is like Ferrari without fuel.
Rooted debloated stock is miles ahead of Samsung's incompetent shadow apps. But even as stripped down as I can make it, the ROM still lags and burns battery in the background. I've tried everything and can't get this beautiful expensive piece of hardware to perform to its specs. I respect others who love it as is, but I've never gotten comfortable with the pen and just want a light, fast tablet with a beautiful screen that doesn't overtax its battery.
I'd switch to Lineage on this device in a heartbeat.
this project still alive? seems dead for me.