Profile cover photo
Profile photo
Wes Goodrich
20 followers
20 followers
About
Posts

Post has attachment
Jon West [electrikjesus]:
Share this please :)
https://youtu.be/5gcEnPJZctI

Post has attachment
Wanted to share a W.I.P..
ValidusOS is very Nice!
PhotoPhotoPhoto
10/15/17
3 Photos - View album

Post has shared content
Updates! October 13th, 2017

Halloween draws nearer, and so do candies and sweet things. Bliss 8.0 (aka Oreo) is coming closer and closer for a public beta candidate.. so what has been going on behind the scenes?

First off, we’re making headway progress! We’ve managed to get a lot of devices up and running. The full list (for now) includes (All usernames are Telegram handles):

Nexus Devices
Nexus 4 (mako, @Nitin1438)
Nexus 5 (hammerhead, @aclegg2011)
Nexus 5X (bullhead, @ideaman924)
Nexus 6 (shamu, @rwaterspf1)

Other
ZTE Warp Sync (warp4, @bcrichster) *Running Nougat for now

And more devices will be on the way in the future!

Secondly, we’re making some good time in development. We’ve been short of staff lately, but that doesn’t stop us from working hard! Unfortunately, I cannot disclose anything related to development, because for one, I don’t know enough to even make heads or tails out of anything. And for another, it’s a surprise. If you really want to follow along as we develop, you can visit us on our GitHub page where we disclose full open-sourced code and also on Gerrit where you can see the tick-tock between the developers minds!

I know you guys were all excited to see Bliss come out soon. We’re making some great headway, and I can promise it will come out soon. But no requests for ETAs, remember!

As for other areas of development, on Bliss-x86 project, we have been making quite a few updates to our Nougat branch in preparation for one final release. New features include updated mesa, added Swiftshader for unsupported GPU hardware (and headless operation) and we are busy, busy, busy on updating the bootable/new-installer to improve on quite a few things. Shoutout to @Vioner for offering to help out there. Bliss-x86 Oreo development is going slow not just for Bliss, but our partners at Android-x86 project as well, and only VM images have been bootable so far. So we are taking some time to explore other options for the issues we are having with Oreo on PC’s. We will update more on this bit at a later date.

Bliss Nougat for Pinebook and Pine64 was updated to support Widevine DRM (for Netflix and other video services) as well as a few minor updates, added features and improvements to Freeform window behaviour. So far no negative feedback from this release, so we are counting that as a WIN!

So that's it for this week guys! It's a Friday, so why not go and party?

Post has shared content
With the way Bliss has taken off in many unexpected ways, we constantly find ourselves looking for new people willing to help us change things in the community.

Our current needs include but are not limited to:

- Project Management
- Social Media
- ROM or App Developers
- PR and Advertising
- Technology Strategists
- Business Management
and many more.

If you are ready to learn something new, or maybe just tired of how the community is running things, consider joining Team Bliss as a start to becoming the change you want to see in the community.

https://goo.gl/forms/PdiaAj1PojosmehK2

Post has shared content
I’d like to take a moment from our normal routine to address a couple issues I’ve observed within the Android development community. Now I’m gonna leave you hanging there for a minute while I tell you a story.

Once upon a time in our little corner of the universe, there were a few people that saw the changes happening with Android development, and saw the need to unite as a team, and create a good solid Open Source ROM for others to use, adapt and add to. This is the team that pretty much started something really good for the community, but it grew too big and went in too many directions for it to effectively fulfil the need to the community it once did.
Fast forward about 7 years, and the growth of that team led to it falling apart. Yes, the ROM lives on under a different name, but the gap in the needs of the community carried on.

There were many that tried to fill that gap, but as time went on, the work needed was too large for just a few to work on and keep up with outside their daily lives. While the rest of the community did nothing to contribute towards the future of the base projects, they only forked it in order to make their own. And this is where the story takes a turn.

There was a need for a new base ROM, because most teams and ROM developers have been spending their time working on bringing up device trees, or taking a fork of someone else’s ROM, and stripping away the branding, added SDK’s, etc. just to get things to a point where forward movement could commence. This is where one of our issues lies too. There is a need for a new kind of base ROM that everyone can use, and while we’re at it, I’d like to suggest we make it easy for people to learn from as well. I’ll be honest and admit that the majority of us really need to work at better documenting our commits and changes, and I’ll leave that at that for now.

The new base should work with ANY device config; los, aosp, du, omni, bliss, etc. We should be keeping the variants list in our Vendor too, and allow other teams to add their device prefixes to it. It should also move away from making changes directly to AOSP I feel. We can use /build/… in our vendor and device configs for any changes needed to be made on top of AOSP for added functions. For this project, we should also consider making the move away from adding directly to frameworks as well, but that is a task easier said than done. And the need for common SDK’s might also not be there any longer, but that is a story for a different post.

Why are we all spending so much of our time working towards what we picture as end goal for our own perspective view, when we could be working together towards a much grander view, allowing all the effort and time being put into getting things up to a point where forward movement can take place to be put into future innovation instead. Doing this will widen the compatibility across the board and speed production, allowing us to only have to keep a few things added to the actual AOSP code in order to truly expand on things.

Now, I do have to hand out a few props to the community for starting on this idea or something similar, but I would also like to say that I feel we might be doing it all wrong. We need to be doing it unbranded and there’s only one small team that has tried that. I know a few on Bliss Family have toyed with this idea as well as AOSP-CAF & GZR, and I give you all mad props, but I feel our biggest hold up on the idea is that we brand it as our own. THIS is where I feel we have built walls as ROM teams. Our branding might identify us and help to add to a prestige or lineage, but I feel it is that ego that has slowly been destroying our community of developers from day one. So this new base must also try and remove the EGO as well. We now have a need to form a team once again that has no wall, no brand, no ego and no boundaries, but has a sole purpose towards setting a new stage for development and allowing forward innovation to move as fast as possible within the community.

And to those wondering why I’m putting this out there? There are some things you might see that need to be changed about the environment around you, but you feel are too big to change by yourself. Don’t hold onto your observations, because they will grow stale and lose their spark. Share the ones you can’t do alone. Because the community is always listening and change will happen, even if you can’t facilitate that change yourself.

I’m open to having a serious conversation about this with any other teams or developers. Our schedule is an open book, so don’t be afraid to reach out to either me.

Post has shared content
I’d like to take a moment from our normal routine to address a couple issues I’ve observed within the Android development community. Now I’m gonna leave you hanging there for a minute while I tell you a story.

Once upon a time in our little corner of the universe, there were a few people that saw the changes happening with Android development, and saw the need to unite as a team, and create a good solid Open Source ROM for others to use, adapt and add to. This is the team that pretty much started something really good for the community, but it grew too big and went in too many directions for it to effectively fulfil the need to the community it once did.
Fast forward about 7 years, and the growth of that team led to it falling apart. Yes, the ROM lives on under a different name, but the gap in the needs of the community carried on.

There were many that tried to fill that gap, but as time went on, the work needed was too large for just a few to work on and keep up with outside their daily lives. While the rest of the community did nothing to contribute towards the future of the base projects, they only forked it in order to make their own. And this is where the story takes a turn.

There was a need for a new base ROM, because most teams and ROM developers have been spending their time working on bringing up device trees, or taking a fork of someone else’s ROM, and stripping away the branding, added SDK’s, etc. just to get things to a point where forward movement could commence. This is where one of our issues lies too. There is a need for a new kind of base ROM that everyone can use, and while we’re at it, I’d like to suggest we make it easy for people to learn from as well. I’ll be honest and admit that the majority of us really need to work at better documenting our commits and changes, and I’ll leave that at that for now.

The new base should work with ANY device config; los, aosp, du, omni, bliss, etc. We should be keeping the variants list in our Vendor too, and allow other teams to add their device prefixes to it. It should also move away from making changes directly to AOSP I feel. We can use /build/… in our vendor and device configs for any changes needed to be made on top of AOSP for added functions. For this project, we should also consider making the move away from adding directly to frameworks as well, but that is a task easier said than done. And the need for common SDK’s might also not be there any longer, but that is a story for a different post.

Why are we all spending so much of our time working towards what we picture as end goal for our own perspective view, when we could be working together towards a much grander view, allowing all the effort and time being put into getting things up to a point where forward movement can take place to be put into future innovation instead. Doing this will widen the compatibility across the board and speed production, allowing us to only have to keep a few things added to the actual AOSP code in order to truly expand on things.

Now, I do have to hand out a few props to the community for starting on this idea or something similar, but I would also like to say that I feel we might be doing it all wrong. We need to be doing it unbranded and there’s only one small team that has tried that. I know a few on Bliss Family have toyed with this idea as well as AOSP-CAF & GZR, and I give you all mad props, but I feel our biggest hold up on the idea is that we brand it as our own. THIS is where I feel we have built walls as ROM teams. Our branding might identify us and help to add to a prestige or lineage, but I feel it is that ego that has slowly been destroying our community of developers from day one. So this new base must also try and remove the EGO as well. We now have a need to form a team once again that has no wall, no brand, no ego and no boundaries, but has a sole purpose towards setting a new stage for development and allowing forward innovation to move as fast as possible within the community.

And to those wondering why I’m putting this out there? There are some things you might see that need to be changed about the environment around you, but you feel are too big to change by yourself. Don’t hold onto your observations, because they will grow stale and lose their spark. Share the ones you can’t do alone. Because the community is always listening and change will happen, even if you can’t facilitate that change yourself.

I’m open to having a serious conversation about this with any other teams or developers. Our schedule is an open book, so don’t be afraid to reach out to either me.

Post has attachment
Jon West (electrikjesus):
Our first video update!! https://youtu.be/VnR3SeTyBgs

Post has shared content
A State Of Bliss - 09.04.2017

The past couple weeks have been very busy for #TeamBliss. We have updates on #BlissOS for the #PINE64, our website, and much much more. But first, a word from our sponsor.

Today's episode is brought to you by PANGO (Parents Against Noobs Going Online)

PSA: If you've ever been answered with a lmgtfy.com link, Please ask your parents permission to connect to the interwebs, thank you.

Now on with the show! Starting off, we wanted to announce that our development team has been working hard to get Bliss on the Pinebook & Pine64 array of devices. We are happy to report that we have the first public beta builds ready for Pinebook and Pine64 owners to flash!! To read more about the development on these devices, follow this link: https://forum.pine64.org/showthread.php?tid=5058&pid=31477#pid31477
The PINE64 also has a release too, and both builds can be found at http://downloads.blissroms.com

Now onto some question and answer time,

Q: Are you guys planning on an O release?
A: No, we're way past the planning stages and knee deep in development :)

We have started working on Bliss OS for Android O, and have been making some pretty steady progress. But I don't want to spoil any surprises, so I recommend you all just be patient and wait to see what we have when WE are ready ;) As always, we will be posting screenshots and maybe even some teaser videos too along the way. Stay Tuned!!

We have also made a few updates to our website, and the latest push includes our new team layout and our maintainer system. This will help everyone looking for their device maintainer or info to find it all in one easy place. Our new maintainer section will also allow us to help any Unofficial Bliss Maintainers by displaying their devices and contact info as well. There's a form from that section for them.
http://blissroms.com

Things are moving forward, slowly but steadily with the nonprofit and Bliss Studios. Although our T-Shirt fundraiser wasn't a success, we are still determined to do the right thing and push forward with our intentions to bring the tools and services needed to develop successfully to the masses of people who want to learn, but cannot afford the tools. Giving them the tools to make their dreams come true, while stimulating innovation with a constant influx of open source projects.

Post has shared content
#TeamBliss is happy to announce that #BlissOS is now running on the #Pinebook! With Pine64 builds to follow very soon :-)
Click here: https://forum.pine64.org/showthread.php?tid=5058&pid=31477#pid31477 for installation and setup instructions via the official Pine64 forums

Post has shared content
Steady progress on getting Bliss to the PINE64 and Pinebook :) We have BOOT!!! and now we get to start playing with all the fun bits ;)

Here is a little more about our progress this weekend: https://forum.pine64.org/showthread.php?tid=4607&pid=31323#pid31323
PhotoPhotoPhoto
8/27/17
3 Photos - View album
Wait while more posts are being loaded