Database Users

Jolla Releases Sailfish OS 1.0

The Wait is Over: Jolla Releases Sailfish OS 1.0 and is Now Ready to
Scale up Globally
Not much else to say ATM

aliander said:
The Wait is Over: Jolla Releases Sailfish OS 1.0 and is Now Ready to
Scale up Globally
Not much else to say ATM
Click to expand...
Click to collapse
That's great news! However, I am a little bit confused about this sentence: "The Sailfish community has already ported Sailfish OS into several devices including major versions of popular Samsung Galaxy, Google Nexus, and Sony Xperia". I didn't see these ports and I try to keep a look out. Where are they?

Daycrawler said:
That's great news! However, I am a little bit confused about this sentence: "The Sailfish community has already ported Sailfish OS into several devices including major versions of popular Samsung Galaxy, Google Nexus, and Sony Xperia". I didn't see these ports and I try to keep a look out. Where are they?
Click to expand...
Click to collapse
Yeah, was wondering quite the same.
Hopefully there will be some more info on that at/after WMC

aliander said:
Yeah, was wondering quite the same.
Hopefully there will be some more info on that at/after WMC
Click to expand...
Click to collapse
I obviously hope they know what they're talking about, but it looks like someone was too hasty and wrote this before it actually happened. I'm very excited to see the release and try porting it when it comes out on some Nexus. It would be great if they released a zip from the Nexus 4 build at MWC.
Sent from my LG-P760 using Tapatalk

Daycrawler said:
I obviously hope they know what they're talking about, but it looks like someone was too hasty and wrote this before it actually happened. I'm very excited to see the release and try porting it when it comes out on some Nexus. It would be great if they released a zip from the Nexus 4 build at MWC.
Sent from my LG-P760 using Tapatalk
Click to expand...
Click to collapse
From reading the press release it appears as if they will release the software for said android devices in the latter half of 2014. I would guess that it mostly works (in house and perhaps for "community" of users with close ties to Jolla) but they are not quite there yet. Otherwise it would be available now. I'd also be interested in seeing how their Sailfish Launcher works. Sailfish does multitasking in a different fashion than android. Wonder how they handle that.
I actually decided to buy the Jolla phone. I live in the US and doubt I'll use it as daily drive since the data will be poor. But I don't mind supporting the company. I'd like to see them succeed.

I'm really curious about Sailfish OS and how it feels in your hand.
Sailfish OS downloadable to existing Android devices
Sailfish OS has been developed to be compatible with commonly available Android hardware platforms. Due to this advanced technology, Jolla is introducing the Sailfish OS experience as downloadable software to devices running Android OS. Users can soon start to enjoy the modern, gesture based Sailfish OS in selected Android devices and also renew the lifecycle of their existing older Android devices.
Click to expand...
Click to collapse
This will be a good way to give Android users a 'taste' of sailfish without actually committing to it.

Daycrawler said:
That's great news! However, I am a little bit confused about this sentence: "The Sailfish community has already ported Sailfish OS into several devices including major versions of popular Samsung Galaxy, Google Nexus, and Sony Xperia". I didn't see these ports and I try to keep a look out. Where are they?
Click to expand...
Click to collapse
Don`t know what do they mean by port to Sony Xperia

Some videos of the Jolla phone at MWC 2014
Here is a "other half" with sensors that makes the Jolla logo light up different colors based on orientation, proximity or flash to alert of a call and you can wave your hand over it to answer with speakerphone or smother it to reject the call.
http://www.youtube.com/watch?v=MdjL8UYaJ34#t=0
I think this is in Italian showing the angry birds other half
http://youtu.be/8S-DugPlvt8
^He doesn't really show much of the OS let's see if we can find another video that shows some of the new features that are coming with the latest update.
Jolla girl demoing the Jolla (in Finnish I'm assuming). This is the latest version of the OS. You will notice some new features like landscape, tethering, fading screen feedback and lock animation
http://jollasuomi.fi/sailfish-kayttojarjestelma-1-0-4-1-ohijarvi-bongattu-jollassavideo/
Engadget interview with Marc
http://www.youtube.com/watch?v=PnB_BXfMreQ#t=66
Phone demo starts at 1:06 so link starts at 1:06
A community member 3d printed and assembled an OLED other half.
http://youtu.be/dLolLNn1WMM
This is the table of other devices running SailFish OS (sounds like Russian to me)
http://www.youtube.com/watch?v=CxWd20JfcU0#t=51
Also in case you haven't seen the latest Nexus 4 sailfish video.
http://youtu.be/oEsNZdcw_cU

Marshmallow Defect Corrections Release?

It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...

The marshmallow update give me some new features and better battery life (though I do own the X Style, not pure). Unless you are dead set on being intentionally obtuse, then this isn't considered an alpha update.
Also the 6.0.1 update is quite minor, the largest change being some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's: http://www.androidheadlines.com/2015/12/google-posts-android-6-0-1-changelog.html

I know the label "alpha" is not not the official label for something like 6.0. But with so many substantial defects, and multiple forthcoming revisions to correct those defects a certainty, that's really what it is IMO. Maybe "public release alpha" would be a better description, since pre-release revisions go through even more defect-ridden levels including pre-release alpha, prior to public release.
Similar situation with previous Android versions, and in fact most software foisted on the public these days (I'm looking at you, Microsoft and Apple). Look at Lollipop and the multiple public release revisions it took to iron out most of the substantial defects, finally, with 5.1.1.
6.0.1 is not just "...some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's...", it also includes defect corrections. (Bluetooth, anyone?) And if the changelog doesn't list a significant number of defect corrections, that doesn't necessarily mean it is already polished at 6.0.1. The fragmented Android ecosystem and separation between Google, phone manufacturers, carriers, and users guarantees a plethora of various non-trivial defects in the ecosystem, many of which Google will address only slowly or even never for most phones.
For example, the memory leak defect in LP was not fixed until 5.1.1. How may revisions and months did that take? How many phones still run pre-5.5.1 with this defect?
One reason I bought the MXPE was the idea that it would be one of the first to get the updates. That turned out to be overly optimistic. It looks like Nexus is the only one still close enough to the source to get timely updates, and it also looks like Google is not pursuing Android defect corrections with any kind of urgency at all nowadays, maybe because the hardware ecosystem is becoming way too diverse to adequately support any more (or maybe because the profits roll in no matter what). Motorola phones, with the Moto alterations to Android, outsider status with carriers, and now hollowed-out Motorola support, appear to be no closer to adequate Android support from Google than any other non-Nexus phone.
"Obtuse"? A "bug" is a euphemism for a defect. Let's stop being obtuse, and call it what it is.
Any other info also appreciated.

You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.

MattBooth said:
You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.
Click to expand...
Click to collapse
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...

Tinkerer_ said:
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...
Click to expand...
Click to collapse
What ad hominem? Your uneducated state affects your ability to understand the nature of Android and software development. It's a perfectly legitimate response to your position. You lack the ability to understand and therefore your argument is flawed. I'm not attacking you, I actually tried to give you some insight into how it works, but you're not really interested and would rather insist on this "public beta" bull.
As far as fixing any "defects" you suppose, you haven't actually listed any so no-one is going to be able to help you with temporary work around without a list of what you feel is broken. I also showed you the changelog, so you can do your own homework to see if your supposed defects are fixed in 6.0.1.
The various hardware configurations doesn't even matter because Android is built to deal with it. So long as the hardware vendors of chips and modules support them properly and give out functioning binaries to OEM's, or proper source code, it's irrelevant. The exact opposite of what you said is true, Google has a very close relationship with it's partners (anyone signed up to their Google programs, to preinstall Google apps). The problem is carriers, who really shouldn't have a say in software on the phones, but that seems to be a chiefly North American problem.
Google doesn't need to have any connection to Android users as customers. Google does not sell Android, therefore you are not Google's customer unless you use a Nexus phone. Google sell the Google Experience, with the Nexus. You are Motorola's customer, and you are using Motorola's branched version of Android. Google doesn't owe Motorola any fixes or patches for their device. Motorola must maintain their own device tree and maintain their own relationships with their partners.
EDIT:
Also, Motorola's problem is resources. They have four version of the Moto X 2015 to deal with, three versions of the Moto X 2014, the new X Force, then the various versions of the G and E to deal with, along with two smart watches, and so forth. Their line up is increasing whist I imagine their development team is not. There was outrage (rightly so) when news broke that the Moto G 2015 wasn't getting the MM update, despite being a couple of months old, and Motorola listened and OTA's are rolling out.

I am asking if anyone can offer any info on anything being done to move toward MM revision with the many significant defects of 6.0 corrected. Read the forums, there are way too many defects with 6.0, it is patently a de facto public alpha, and we are tracking the usual pattern where it takes 3 to 5 revisions before an OS major rev is ironed out enough that upgrading will not cause more problems than it fixes.
There are always excuses made for why there are so many defects in software. There is a euphemism for "defect" everybody uses, "bug". Everyone has been making excuses for so long about shoddy workmanship and inadequate testing and correction of software, with the "bug" euphemism to minimize the reality that these are defects, that we are all just to suppose to accept systems ridden with faults without complaint. It's unacceptable. It can be done better. Part of why it doesn't get better is because everybody says "that's just the way it is, deal with it". With mountains of byzantine excuses and even ad hominem attacks (as here).
This thread was not started to start a tit for tat ad hominem back and forth, nor to post long essays detailing excuses for the pathetic status quo of the fragmented Android ecosystem with respect to defect causes and distributions. It was started looking for any info about work being done to fix the stock MM defects. Still seeking info.
TIA.

You should probably check the definition of ad hominem. There was no attack on you as a person, just pointing out that your uneducated state with regards to knowledge about software development affects your ability to call judgement on this.
But you haven't listened to a single word I've said and still maintain a shoddy position, so I would suggest to anyone else who reads this to simply ignore you as a troll.

Tinkerer_ said:
It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...
Click to expand...
Click to collapse
I think we'll close this debate. There are no real "Android" insiders on XDA, so asking for update info which is privy to Google is perhaps somewhat futile.
On a related note, XDA have a few dedicated "Android Fora", such as this complete Category where non-device specific discussion and indeed conjecture takes place. Perhaps you could take a look there and see what transpires?
Thanks

Former Cyanogen developer - "if you have a CyanogenOS phone and can disable updates o

Former Cyanogen developer - "if you have a CyanogenOS phone and can disable updates o
https://www.reddit.com/r/oneplus/comments/5k8ppv/former_cyanogen_developer_if_you_have_a/
TL;DR provided by /u/Nickers77
CyanogenOS team was mostly fired, rest quit.
Core developers are gone, don't download any updates.
Reason for this change is so they can monetize android OS, presumably by selling consumers to adware companies.
They can push system-level packages to your phones undetected and with no way to stop.
Google now competitor, but since it doesn't have access to Google calendars and searches like the entire of the Google system, will rummage through your data to find relevant info.
Click to expand...
Click to collapse

How can you do this on a stock device?

Go go Settings ==> Apps ==> Show System (behind the 3 dots on Top right) ==> open "Systemupdates" ==> check "disable"
Info is from the Reddit article from the first post...I don't know if this is enough, but I did this on my Oneplus One.

Boy that went downwards real quick. First the death of CyanogenOS, then the death of CyanogenMod, now this. Guess Cyanogen Inc won't be around for too long.

GXGOW said:
Boy that went downwards real quick. First the death of CyanogenOS, then the death of CyanogenMod, now this. Guess Cyanogen Inc won't be around for too long.
Click to expand...
Click to collapse
It was foolish trying to make profit from CyanogenMOD ...when COS was created I was why? why? ...at least now this is dead so it's LineageOS or roms based on that which is cool
I hate this corporate D, who tried to make profit from open source code

evronetwork said:
It was foolish trying to make profit from CyanogenMOD ...when COS was created I was why? why? ...at least now this is dead so it's LineageOS or roms based on that which is cool
I hate this corporate D, who tried to make profit from open source code
Click to expand...
Click to collapse
Well putting an asshole like McMaster in the CEO position wasn't one of their smartest moves either. The whole company was just one downward spiral. It's a shame, but that's how things went, unfortunately. Let's hope LineageOS will take of as the worthy CM-successor. Hopefully no-one will have the bright of starting something like Lineage Inc.

GXGOW said:
Well putting an asshole like McMaster in the CEO position wasn't one of their smartest moves either. The whole company was just one downward spiral. It's a shame, but that's how things went, unfortunately. Let's hope LineageOS will take of as the worthy CM-successor. Hopefully no-one will have the bright of starting something like Lineage Inc.
Click to expand...
Click to collapse
Well LineageOS inc would be terrible as a name, heck I find the name bad but as long as it's open source and similar to CyanogenMOD I'm fine
Just wish they would try to reduce it's size, ~400MB for a custom rom? that's terrible

I'm baffled that everyone is surprise with this....any manufacturers or devs can push system-levels packages into their rom without user ever noticing it whether in full roms or via OTA updates....
remember this articles http://www.kryptowire.com/adups_security_analysis.html ??? it is the same thing happening on COS and no one notice it until Kryptowire discovered it last month....

I worked at Cyanogen.
They fired the OS team at the end of July. Of the rest, half were gone by the end of November, and the only people who weren't looking for another job were upper management.
They shut down the Seattle office at the start of December. They're selling off all the equipment there (except the large televisions we used for all hands meetings for some reason). That leaves a very small subset of the developers.
They have nobody who knows how to create a new android build. They have nobody who knows how to upload a build to aerios (the OTA system). They have nobody who has write access to aerios (though they could log into cassandra and add someone manually -- hell, that's what I had to do). They have nobody who can authorize a build to go out to end users. I think they have just barely enough technical knowledge to shut off our AWS services (but I can't be sure about that -- we enabled termination protection for some instances, and that might trip them up). They could potentially hire contractors for QA, though.
Given what level of access they have and the things they were discussing when I left, if you have a CyanogenOS phone and can disable updates on it, do so.
Click to expand...
Click to collapse
Taken from Reddit

LineageOS and "project treble"

A question concerning LineageOS and "project treble":
Will LineageOS be available/compatible for/with every phone that is sold with Android 8.1?

Short answer: No.
Long answer: LineageOS support is made possible by drivers and source code for various devices being available. If they aren't, then the amount of work required to support a device is nearly impossible.
Project Treble makes security updates easier for OEMs to maintain. It does not mean they all use exactly the same hardware.

But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?

Nexxus23 said:
But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?
Click to expand...
Click to collapse
I think same but there is to little information about it. In that case if i install any UnOficial LineageOs and it works fine i could instal latter any oficial LineageOs trable (without vendor partition) and it should work.
But there is not any oficial explanation about it.

If only it were so easy .....
Nexxus23 said:
But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?
Click to expand...
Click to collapse
On the one hand, yes, it might be not all that difficult to contrive an LOS build for originally configured as Treble-compliant devices going forward, but the vast majority of devices running LOS are never going to see a Treble-compliant ROM for a starting point in the first place. So what you are "missing" is that re-writing the HAL for every current LOS device would be a HUGE pain in the rear end. Asking for that much re-write effort is, well, not something I would consider to be terribly realistic, or even feasible. Eventually - perhaps. In any foreseeable time frame going forward - not much of a chance. You need to keep in mind that many if not most people probably head towards Lineage because their devices are no longer supported in the first place. Sure, some are just allergic to vendor bloatware or want a more generic UI, but I would wager on vendor neglect as the main driver. Could be wrong .....

Lineageos 15.x/16.x and nexus 5 in the future ?

Hello,
I am a user of Google Nexus 5 smartphone (hammerhead) and since a few weeks, there were less LineageOS updates.
We don't see for the moment this devices on roadmap support for LineageOS 15.x/16.x.
Is there any chance to have this version on Nexus 5 in the future ?
We'll really appreciate this, as we use daily LineageOS and love it !
Thanks in advance.

nexus5yaute said:
Hello,
I am a user of Google Nexus 5..........
Click to expand...
Click to collapse
I don't have this specific device myself but, It looks like the last Official Lineage Team Maintainer no longer has this device any longer that resulted in it being dropped Officially by LineageOS as seen on the following link.
https://wiki.lineageos.org/devices/hammerhead
This doesn't mean that all is lost for this device...
There's a handful of other Custom Firmware (to include Unofficial LineageOS builds) within the following area of the forum that's specific to your device as well.
https://forum.xda-developers.com/google-nexus-5
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

Recent Android on Nexus 5
Thanks for your reply and information Ibuprophen
I just check some others alternatives of LineageOS ROM for Nexus 5 and Oreo, but for most, it seems not yet available or not really updated regularly (and we especially take care of monthly software Security Patch).
We'll have to check, but if someone know a well maintained Oreo ROM for Nexus 5, this may be probably the good solution.
Finally, Nexus 5 hardware is great, and I suppose that several users continue to have them currently and will be happy to have a recent Android software with regular updates.
Many Thanks!

U may want to check e.foundation. they're currently supporting the Lineage 14.1 base for the N5. I don't know if you'll like the project. But you can check and see.