After nearly one year's silence, SwipeBack is now back alive, known as SwipeBack2.
SwipeBack2 is the continue of SwipeBack. It has still the basic feature, swipe-to-return gesture, inspired by the library SwipeBackLayout written by @Ikew0ng(a.k.a. IssacWong, 碎星iKe, 碎iKe). It provides a smooth, nature-like and highly customizable swipe-to-return gesture. This module is initially a wrapper of SwipeBackLayout in Xposed, and was welcomed widely by Xposed users. Gradually it has gained much new features that is more than SwipeBackLayout.
If you have installed the old SwipeBack, please uninstall it first, and then you can install SwipeBack2
Features:
* Swipe-to-return gesture
* Per-activity settings which means you are able to customize settings on <strong>each page of each app</strong>
* Experimental hacks for Lollipop (may not work, use with caution, do not turn it on globally)
* More experimental features are coming in future releases.
Note that SwipeBack2 is now only a rewrite and a port to Lollipop (but it still works fine on ICS/JB/KK). It has many work to-do, as:
* Pure-gesture mode (disable scrolling effects, enables compatibility with apps that consist of Fragments but not Activities, and can work with Browsers)
* Fully-costomizable trigger area (at <strong>any</strong> position on the edge, to fix compatibility with apps that has a gesture like drawers already)
* Automatic bug report and crash log submitter
* More (<strong>advices are always welcome)
SwipeBack2 is free software released under the terms of GNU GPLv3. Source code available at https://github.com/PaperAirplane-Dev-Team/SwipeBack
Download:
From Xposed Store: http://repo.xposed.info/module/info.papdt.swipeback
From Google Play Store: https://play.google.com/store/apps/details?id=info.papdt.swipeback
Changelog
1.0.0
- Initial Release
FAQs:
Q: Why renamed to SwipeBack2?
A: Because SwipeBack2 is completely rewritten, and is refactored to have a better stability and flexibility. And another reason is, that SwipeBack (us.shandian.swipeback) is blacklisted by Alipay because of the unsecure SwipeBack, so I just renamed it to SwipeBack2 (info.papdt.swipeback), hoping that it will not be blacklisted any more.
Q: Would you add feature X / fix bug X?
A: Feel free to send emails or open issues on GitHub page. I may not have time to reply to you all, but I will take a look at bug reports and feature requests and have the resonable ones implemented in new releases.
Q: SwipeBack is great! Do you accept donations?
A: Well, not now.
XDA:DevDB Information
SwipeBack2, ROM for all devices (see above for details)
Contributors
PeterCxy
Source Code: https://github.com/PaperAirplane-Dev-Team/SwipeBack
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Beta
Created 2015-03-31
Last Updated 2015-03-31
I have been building a custom LineageOS 14.1 for a few Moto phones (G4, G4 Play, G5 Plus) with the intention of including the MicroG Project to replace Google Play Services. So far, I have successfully built this ROM the for G4/G4 Play, using the patches on github: ( microg/android_packages_apps_GmsCore/tree/master/patches - sorry, can't post links with my account yet ) to integrate seamlessly into the system. However, when I build for the G5 Plus, MicroG is not registering the location services properly to the system. ("Your system does not support this UnifiedNlp package")
I am building with the latest boulzordev sources on github for the device tree, kernel and vendor blobs.
(Thanks @vache, @fAIyaZ, @SJR (Sam), @Alberto97, @Mandy $ingh and everyone else for all your hard work on this device!)
I'm completely stumped as to why this device would be having issues with MicroG. Any ideas out there?
elisam98 said:
I have been building a custom LineageOS 14.1 for a few Moto phones (G4, G4 Play, G5 Plus) with the intention of including the MicroG Project to replace Google Play Services. So far, I have successfully built this ROM the for G4/G4 Play, using the patches on github: ( microg/android_packages_apps_GmsCore/tree/master/patches - sorry, can't post links with my account yet ) to integrate seamlessly into the system. However, when I build for the G5 Plus, MicroG is not registering the location services properly to the system. ("Your system does not support this UnifiedNlp package")
I am building with the latest boulzordev sources on github for the device tree, kernel and vendor blobs.
(Thanks @vache, @Faiyaz,@SJR (Sam), @Alberto97, @mandy $ingh and everyone else for all your hard work on this device!)
I'm completely stumped as to why this device would be having issues with MicroG. Any ideas out there?
Click to expand...
Click to collapse
That's interesting, personally I have not used MicroG so not sure where to direct you to for help. You could try taking a logcat and posting it so that other devs could check it out and try and help you! Good luck mate!
Sam
Great news! I finally figured it out - based on issue #55 in microg's Github repos - https://github.com/microg/android_packages_apps_UnifiedNlp/issues/55
I'll post my resolution here for reference.
The basic issue was that in the overlay included in the device tree, there is a config that is blocking network location services from working:
In the file device/motorola/potter/overlay/frameworks/base/core/res/res/values/config.xml, starting on line 204, I removed the following code
Code:
<!-- Enable overlay for all location components. -->
<bool name="config_enableNetworkLocationOverlay" translatable="false">false</bool>
<string name="config_networkLocationProviderPackageName" translatable="false">com.qualcomm.location</string>
<bool name="config_enableFusedLocationOverlay" translatable="false">false</bool>
<string name="config_fusedLocationProviderPackageName" translatable="false">com.qualcomm.location</string>
The build compiled smoothly and my issue was gone.
Was this included in the code intentionally, @vache, @SJR (Sam), @Mandy $ingh or @Alberto97?
elisam98 said:
Great news! I finally figured it out - based on issue #55 in microg's Github repos - https://github.com/microg/android_packages_apps_UnifiedNlp/issues/55
I'll post my resolution here for reference.
The basic issue was that in the overlay included in the device tree, there is a config that is blocking network location services from working:
In the file device/motorola/potter/overlay/frameworks/base/core/res/res/values/config.xml, starting on line 204, I removed the following code
The build compiled smoothly and my issue was gone.
Was this included in the code intentionally, @vache, @SJR (Sam), @mandy $ingh or @Alberto97?
Click to expand...
Click to collapse
I'll let the others speak, but it was probably setup just for Lineage to build. You got it working though! Good on you mate!
I'm using @SJR (Sam) LineageOS 14.1 builds and I'm very interested to use the MicroG GPS/Map Services (UnifiedNlp, LocalGsmNlpBackend) but was not able to activate them by installing from F-Droid repositories. So I think either a ZIP install or modified LineageOS 14.1 is needed. @elisam98 could you may help by sharing with the userbase?
Hello there!
I tried to use MicroG (and NanoMod) with AOSP Extended and Validus, both 8.1. It looks like qualcomm location service is preventing nlp from work So I would like to ask: is it any way to fix this issue without recompiling all the system? Or, maybe, anyone here have made builds with this issue fixed?
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
why alpha? when can we expect a stable build?
shawon11 said:
why alpha? when can we expect a stable build?
Click to expand...
Click to collapse
Sorry bro but this is not my work I am just sharing good TWRP:good:
Azizbagwan said:
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
Click to expand...
Click to collapse
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
robbayani said:
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
Click to expand...
Click to collapse
Project Treble is the Answer
The reason manufacturers have such a hard time pushing out prompt updates is because of all the work that has to go into getting the operating system to communicate with the hardware.
Traditionally, it worked something like this: the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software–technically referred to as vendor implementation—also had to get updated. That’s a lot of work.
So, starting with Android 8.x (Oreo), Google separated the two. That means the Android OS itself can be updated without having to touch the vendor implementation. That, in turn, can be updated by itself if needed.
To put that in full context, before an update can be pushed out to an Android 7.x (or earlier) device, not only does the Android OS code have to be updated, but so does the low-level hardware code, which is generally maintained by the chip maker. So, for example, if Samsung wants to push an update to one of its phones, it has to wait for Qualcomm (or whoever made the chip) to update its code to work with the new Samsung code. That’s a lot of wheels turning at once, and each one is dependent on the other.
With Android 8.x and beyond, it won’t be like this anymore. Since the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
This should dramatically speed up the update process—in theory, at least. Updating devices will still be in the manufacturer’s hands, and since the first Oreo devices outside of the Google-maintained Pixel line are just now rolling out, we haven’t yet had a chance to fully see this in practice. Hopefully, it actually makes a significant change to the speed in which updates are written and pushed out.
Will My Device Benefit from Project Treble?
Now that’s the million dollar question, right? Unfortunately, the answer isn’t so simple (surely you didn’t expect it to be). That said, here are some facts:
If your device never gets updated to Oreo, it will never get Project Treble. No way around that. Sorry.
If your device does get updated to Oreo, it’s still not required to support Treble—that’s up to the manufacturer.
If you buy a new phone that runs Oreo out of the box, it is required to support Treble out of the box.
In short: Treble support on updated systems is still up to the manufacturers, but new Oreo devices will be required to support Treble moving forward.
So, for example, the Pixel 2 already supports Project Treble. The forthcoming Galaxy S9 will also support Treble out of the box. Google also updated the Pixel 1 to support Treble, but it’s unfortunately it looks like Samsung left it out of the Oreo build for the Galaxy S8.
If you’re curious about your own device, Android Police has a running list of all devices that will get Treble support, as well as a which ones will get updated to Oreo without Treble.
Android OS updates have been a constant point of contention for many years now, so it’s good to see Google finally addressing the issue. With any luck, this will put all Android devices closer to parity with Apple in terms of device updates.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Bliss is pleased to present to you
Bliss-OS for PCs based on Android 10
An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook, Windows/Linux PC or tablet released in the last 4 years
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss-OS comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
First, a little bit about this project...
Starting in Android Pie, Bliss OS took a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, and Android-x86 Project, we have now adapted that method to be a bit more streamlined, and packaged it up so that it can work a bit more dynamically. The manifest can be found at: https://github.com/BlissRoms-x86/manifest/tree/q and the new patching system and build script are all included in https://github.com/BlissRoms-x86/vendor_x86/tree/q
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well.
!!UPDATE!! 07.01.2020
These builds are now made with Android-Generic project
Made with Android-Generic v1.1 - Android for PCs & GSI devices
AG For ROM developers
Android-Generic means there is finally something out there that helps to bring all the PC commits/setup/etc to your current ROM's build environment, working towards making the process easier for everyone involved moving forward. We also added a few smart features to the vendor toolkit as well, like commit resolution resource sharing, easy methods to add your vendor, easy methods to create manifest backups, and the scripts do most of the work for you already, with the exception of fixing some patch conflicts (the toolkit is smart enough to find potential fixes on it's own based on all the devs that contribute their patch resolutions back to the main repo). We have also added the option for Customizations to be chosen/placed on top of your ROM for added customization/branding options. We're trying to change the game here and allow many more ideas for PC to arise than what Team Bliss would have been able to do on their own. All the info needed to get started can be found in the project README.md, including links to the development chats for each side of the project : https://github.com/android-generic/vendor_ag
AG For users of Bliss OS, Android-x86, etc.
This means there is going to soon be a lot more options out there to choose from for running Android on your PC. And every new ROM added to the main repo means more and more ROMs will have an easier time porting their work to PCs as well.
Now, on to more info about Bliss
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
Bliss' Android-PC Project
https://github.com/Android-PC
Bliss OS Source
https://github.com/BlissRoms-x86
Bliss OS Kernel Source
https://github.com/BlissRoms-x86/kernel_common
Bliss OS downloads can be a bit confusing to most users initially. We have tried to slim down the methods for which there can be differences by revamping our downloads section of the websites. For newbies, this will help a lot. For advanced users though, like all of you We have a little Q&A for what the filenames mean below:
Build Types Explained:
Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64"
Kernel Branch: "_k-k4.19.50-ax86-ga"
Mesa Branch: "_m-18.3.5-pie-x86-llvm80_"
libdrm Branch: "_ld-2.4.99-ma-p"
drm_gralloc Branch: "_dg-pie-x86"
Some uncommon flags:
drm_hwcomposer: "_dhpie-x86"
Firmware Branch: "_fwdev-kernel.org"
llvm Branch: "_lv18.0.3-llvm9.0"
Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux)
-ga/gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
-yl : Means that kernel includes the latest Intel BayTrail/CherryTrail commits from @youling257
-jw/jwd/jd: Means that kernel includes the latest Intel BayTrail/CherryTrail commits from https://github.com/jwrdegoede/linux-sunxi
Q: OK, So I have a Blah-Blah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
k4.9 These are considered the most "Stable" builds, they will work across most older and some recent devices.
k4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
k4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
k4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
k4.19+ This is our current mainline kernel branch. Intended for newer devices. Even more touchscreen support and ACPI support
k4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
k5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.
Bliss OS 12.0 Alpha Downloads
These are to be considered "in development" and are in no way intended for general use. We will expect any bug reports or issues to be accompanied by a log of some sort. Whether it's in the form of an attached file, or a link to a hastebin or something. It just has to be a log. If you post a screenshot, saying "it no workie", you won't get very far. We tend to only help those who help themselves.
With that being said, the downloads are a little hidden this round. We added a secret download button to the website for out Bliss OS 12 alpha builds, and the secret code to reveal it is hidden within this first post (somewhere)
Please visit https://blissos.org and the Bliss OS 12 alpha testers section is just below the Downloads section. When that section is in view, please type the secret code and the download button will show.
Have fun reading, and hope to see some bug reports soon
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with the methods of install as well as what could go wrong before moving forward. Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
The Instructions
We have moved the instructions to be a part of our docs site
Thanks, and keep scrolling for FAQ & Updates
This is a development alpha release, so there will be bugs.
Known Issues:
Sleep Issues on non-Vulkan machines. This is due to a bug in drm_gralloc/drm_hwcomposer. Haven't found a fix for it for Pie or Android 10. FIX: Run in Vulkan Mode if you can
Lockscreen shows, then the device crashes. Please see above issue as this is a direct result of said sleep issues
I can't install Magisk in this release, why? This is due to the lack of a ramdisk/boot image this round. Due to changes in Android 10, this was a change we needed to make.
For All Other Issues:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
After downloading the Catlog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving.
As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
Manual Logging:
Use the alt-f1 console, and in the console, type:
Code:
logcat > sdcard/log_name.txt
Then alt-f7 to get back to the Android UI, and replacate the issue. When done, use alt-f1 to go back to console and ctrl-c to stop the logging.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the forum with a brief description of the error.
Only issues with adequate info and logs attached will be taken seriously. Thank you.
@jackeagle @electrikjesus @rwaterspf1 @Makaveli_da_dev @ElfinJNoty @BitOBSessiOn @customworx
@nilac @sixohtew @aclegg2011 @Roger.T @T.M.Wrath @kanttii @REV3NT3CH @techfreak243 @SuperDroidBond @USA_RedDragon @bcrichster
@DeadmanxXD @krittin98 @blackscorpion @TechExhibeo @DroidBot @Siphonay @pacer456 @nitin1438 @theGeekyLad @kunalshah912 @regalstreak @LordArcadius
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
About Bliss Family of ROMs
Bliss Family of ROMs aims to develop and maintain various OS & software projects for educational and the Android community building purposes.
Team membership consist of and provides:
Training, development opportunities, design opportunities, build servers when available, download servers, design & development software, as well as a stress free team oriented community of professionals and mentors in all fields revolving around Android development. To join our team, please visit either of our websites, and find the Join Team Bliss link.
If someone wants to donate, please do so via this PayPal link:
PayPal Link
WE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
We receive a small donation each time you make a purchase with “Amazon Smile”:
https://smile.amazon.com/ch/82-3580195https://smile.amazon.com/ch/82-3580195
Notice
The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.
We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
[ul]
[li]Please do not ask for ETA's[/li]
[li]We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts[/li]
[li]Team Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.[/li]
[/ul]
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.
Websites
https://blissroms.com
https://blissos.org
Official Platform Links
https://www.facebook.com/BlissFamilyOfROMshttps://www.facebook.com/BlissFamilyOfROMs
https://twitter.com/Bliss_ROMshttps://twitter.com/Bliss_ROMs
https://www.instagram.com/blissroms
https://t.me/blissx86https://t.me/blissx86
Thank you for using Bliss! And as always: #StayBlissful
XDA:DevDB Information
Bliss OS (x86) for PC's - 12.x Development - Android 10, ROM for all devices (see above for details)
Contributors
electrikjesus, jackeagle
Source Code: https://github.com/BlissRoms-x86
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP, LOS, Android-x86
Version Information
Status: Testing
Created 2019-11-16
Last Updated 2020-07-02
FAQ & Questions:
For all FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2019.11.19
https://forum.xda-developers.com/showpost.php?p=80950983&postcount=15
Second round of updates - 2019.12.16
https://forum.xda-developers.com/showpost.php?p=81122057&postcount=80
Bliss OS 12.2 Alpha Updates - 2019.12.28
https://forum.xda-developers.com/showpost.php?p=81329287&postcount=160
Bliss OS - Yantra - 12.2 Beta Release - 2020.02.05
https://forum.xda-developers.com/showpost.php?p=81688893&postcount=229
Bliss OS "Yantra" 12.3 Beta Release - 2020-02-23
https://forum.xda-developers.com/showpost.php?p=81845175&postcount=296
Bliss OS "Yantra" 12.4 Release Candidate 1 - 2020-02-27
https://forum.xda-developers.com/showpost.php?p=81880187&postcount=309
Bliss OS "Yantra" 12.5 Release Client 2.1 - 2020-03-26
https://forum.xda-developers.com/showpost.php?p=82110111&postcount=389
Bliss OS "Merkaba" 12.6 Release Client 2.2 - 2020-05-05
https://forum.xda-developers.com/showpost.php?p=82490635&postcount=451
Bliss OS "Merkaba" 12.6 Release Client 2.2 - AMD - 2020-04-23 & Bliss OS Lite Alpha Release - Vulkan - 2020-05-31
https://forum.xda-developers.com/showpost.php?p=82731139&postcount=499
Bliss OS "Sri" 12.8 - Introducing Android-Generic v1.1 Vulkan & Generic-Intel Builds - 2020-06-30
https://forum.xda-developers.com/showpost.php?p=82968733&postcount=543
AG-10 Bliss OS 12.12 - Generic Build - 2020-10-07
https://forum.xda-developers.com/showpost.php?p=83661857&postcount=674
AG-11 & Bliss OS 14.3 - Generic Build - 2021/06/17
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you Bliss-OS for PCs based on Android 10 An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook...
forum.xda-developers.com
Bliss OS 14.3 - Generic 5.4 Builds (32bit FOSS / 64bit Gapps) - 2021/06/18
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you Bliss-OS for PCs based on Android 10 An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook...
forum.xda-developers.com
Bliss OS 14.3 - Generic x86_64 - kernel-5.10.42 - 06.26.21
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you Bliss-OS for PCs based on Android 10 An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook...
forum.xda-developers.com
Bliss OS 14.3 FOSS - x86/x86_64 - kernel-5.10.50 - 07.24.21
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you Bliss-OS for PCs based on Android 10 An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook...
forum.xda-developers.com
Reserved
great
working smoothly as always, keep it up! btw why is there windows logo on the pictures lol
kc4knc said:
working smoothly as always, keep it up! btw why is there windows logo on the pictures lol
Click to expand...
Click to collapse
It was a Windows tablet mockup I used for the image, in order to help signify our target device type
I really like the secret code idea
Although I copied the link instead of writing the code since It was easier at that point^^
Edit: nvm I just noticed that u hinted the code was hidden in ur post XD
Update on known issues
Chrome not working correctly - Please go to recents, and click the chrome icon, then click freeform. This will allow chrome to not close. A better solution is to download Brave browser from Play Store. The next update will include LOS's Jelly browser instead, since that's a small browser source we can add to the manifest.
Play Store sign-in not showing anything - Please open this window in freeform and resize until you can see what is presented on screen.
where i can type the secret code? no space, it can't type.
I can't find the type the secret code space.
youling257 said:
where i can type the secret code? no space, it can't type.
I can't find the type the secret code space.
Click to expand...
Click to collapse
Just click on that and start typing. It will change when you have finished typing.
bfmetcalf said:
Just click on that and start typing. It will change when you have finished typing.
Click to expand...
Click to collapse
Android chrome, finger click that, no pop up android screen keyboard for type.
youling257 said:
Android chrome, finger click that, no pop up android screen keyboard for type.
Click to expand...
Click to collapse
Hmmm, interesting. Maybe do it on a computer and send the link to your phone.
bfmetcalf said:
Hmmm, interesting. Maybe do it on a computer and send the link to your phone.
Click to expand...
Click to collapse
Correct. Since this is for PC's I figured only PC users would try it.
youling257 said:
Android chrome, finger click that, no pop up android screen keyboard for type.
Click to expand...
Click to collapse
I could add an editable message box for people to enter the code. This would at least prompt the on-screen keyboards for tablets.
youling257 said:
where i can type the secret code? no space, it can't type.
I can't find the type the secret code space.
Click to expand...
Click to collapse
I use js to just listen to all keystrokes on the page, kinda like the old konami code for video games. So whenever get the right code, it just triggers the action.
Edit: I added a textbox to that section of the website. This should help some cases a little. Still doesn't work from mobile devices though. Will likely remove the whole thing I'm a few more days
Edit2 - Updated with Bliss-Bot, and she's programmed to recognize mobile input too
electrikjesus said:
Correct. Since this is for PC's I figured only PC users would try it.
I could add an editable message box for people to enter the code. This would at least prompt the on-screen keyboards for tablets.
I use js to just listen to all keystrokes on the page, kinda like the old konami code for video games. So whenever get the right code, it just triggers the action.
Edit: I added a textbox to that section of the website. This should help some cases a little. Still doesn't work from mobile devices though. Will likely remove the whole thing I'm a few more days
Click to expand...
Click to collapse
it can't listen screen keyboard type code.
connect bluetooth keyboard, it can listen bluetooth keyboard type code.
Hi, What is the secret code please send me at
[email protected]
Bliss OS 12.1 Alpha Updates - 2019-11-19
!! Please remember to not quote these update posts, or any of the OP's !!
We're back with some more Bliss goodness for you all. Made a few updates to google & OpenGapps permissions, as well as a bunch more updates for init, sleep states, etc. I am still not able to get a generic ARM compatibility library to work, I've tried Houdini two different ways now with no luck. Will keep plugging away at this though, because I don't want to restrict the native bridge abilities to just Intel CPU's. I'd like to find a more generic method for us all.
PLEASE NOTE I recommend everyone testing to also use this in Vulkan mode, as I am considering making it the default. This can be done from the Advanced grub menu if you installed using the bootable installer, or if you used a different grub, you will want to add "VULKAN=1" to the grub entry before the word "quiet"
Builds being uploaded:
Bliss-v12.1--OFFICIAL-20191117-android_x86_64-201911171948_k-undefined_m-q_ld-q_dg-q_dh-q.iso
General Updates List:
Updated Styles and Wallpapers
Added sleep button to the power menu. Access it using Ctrl+Alt+Del or the three dot menu from Taskbar.
Bluetooth updates & fixes
Taskbar freeform launcher updates.
TinyALSA added to try and help fix the volume buttons not working on some devices
Added more boot support for nvme type SSD's
Some upstream updates from Android-x86 project's Pie-x86 branch
and much much more, check the changelog. (yeah, got that working this round too)
Known new issues:
AOSP Gesture navbar crashes. Just don't try to use it yet.
Sleep states aren't working right on many machines. Some can cause SystemUI to restart
Power buttons still don't work on a most machines.
Volume buttons might not affect media volume, use 3rd party EQ or volume control.
Changelog:
Code:
====================
11-17-2019
====================
* bootable/newinstaller/
43cdc13 Add Bliss OS configs and changelog
31b7bb2 Update filename
3a56105 Add old modprobe entry
8481503 Add back nvme device mounting
4fdb5ba link /lib/modules as well
fb1d593 Move hotplug detection to before we make /dev/block
f23e176 Add date to filename
394ccdb DO NOT MERGE: Mount system partition at root.
57994a8 1-install: avoid unnecessary errors from cp
* device/generic/common/
05ad776 Remove for now
2102b0d Changes for houdini
5e08387 system prop changes for init
bdb7cba fix a few things on init
3013fd3 Add freeform and mic settings
d0ae829 Remove Chrome
0f51c79 Fix for enable_nativebridge on Q
099c9b2 Revert "Add extra packages for our gms "
e7ea0fe mount kernel/debug to help with some webview issues
7dea1e2 Add back swrast gpu drivers
* vendor/x86/
ccacff3 Patch updates - 11.16.19
====================
11-16-2019
====================
* device/generic/common/
7ab69d5 more supported disk types
bbb6717 Add nano local lodule
511044a init.sh: disable offlining of non-boot CPU of Teclast X80 Power
a39b3b2 kernel.mk: remove obsolete rules
d2f9047 init.sh: add quirks for Acer SP111-33
4f56c34 switch to libhoudini for native-bridge
cc10dd6 Add extra packages for our gms
f658c6c Adjust bootanimation size
e9e890b Add bliss_priv if available
* frameworks/base/
035a95de93d Remove extra break
====================
11-15-2019
====================
* frameworks/base/
f030f22d337 Align the pageBlockOrder to the kerne 4.19 kernel
89e80f054ed Enabling suspend on IVI after clicking sleep from the power button menu.
bea45906663 GlobalActions: Handle 'sleep' action
====================
11-14-2019
====================
====================
11-13-2019
====================
* device/generic/common/
7d8e816 Fix formatting
cfca6ed Missed a microG change
7786c0b Updates for microG
437c5f7 Switch back to -if-exists
2343bc6 Switch to vendor/google/chromeos-x86/sepolicy
ec56bce updates for included external sources
* frameworks/base/
625babaeaad microg-sigspoof for Q
* vendor/fdroid/
c8e85bb Fix google maps conflicts
* vendor/x86/
673be85 Add spoofing for microg
====================
11-12-2019
====================
* device/generic/common/
ec56bce updates for included external sources
daf56bf Move inherit to the right place
86739eb Inherit more vendor items
260aee3 Remove redundant apps now
* vendor/fdroid/
b091524 Add updates for Q
====================
11-11-2019
====================
* device/generic/common/
d185d61 Update to new Taskbar and TSL
* packages/apps/Settings/
8f4b5b94ac Settings: Add BlissOS Header
* vendor/themes/
b25724c Accents: Add Mint accent color
====================
11-10-2019
====================
* device/generic/common/
87be5a9 Add manufacturer to bliss device string
* frameworks/native/
21d752c2b SurfaceFlinger: enable console management
====================
11-09-2019
====================
* device/generic/common/
10abc6f This one isn't needed
8d514be Inherit a few more Bliss configs
d526a0f Add in extra .idc configs
b40f4d2 Update to new Taskbar
* vendor/themes/
ab3e099 vendor/themes: Remove Fonts
====================
11-08-2019
====================
* device/generic/common/
69b4f40 Add bliss properties
ea2e71b Revert "Add koush/superuser if available"
ac34f7c Switch back tocyanogenmod.superuser
e429be6 Add koush/superuser if available
* vendor/themes/
5a27611 vendor/themes: Disable Fonts building
====================
11-07-2019
====================
* device/generic/common/
1d23e5a init.sh: fix virgl support of newer kernel
3471811 Switch to houdini instead of nativebridge ARM on x86
* vendor/themes/
26019d5 Accent: Cleanup
d84b215 AccentOverlays: Update all overlays packages
b4c959c AccentOverlays: Add ThemePicker Category
4a60cd7 Update .gitreview
0d00525 Disable Package themes
f9e7643 Disable Primary Themes
53eb275 themes: Disable QS Styles
* vendor/x86/
57ed6d1 Updates for Q
====================
11-06-2019
====================
* device/generic/common/
1c66724 Formatting changes
f686649 Add vendor/magisk if available
c3dee8b Fix adding superuser with app
====================
11-05-2019
====================
* frameworks/av/
cc18a00cc audiopolicy: support extended feature in audiopolicymanager
bf2759711 audiopolicy: make audio policy extensible
43617da13 Explicitly initialise base class in copy constructor
21d7e26ad soundtrigger: fill in default extras from dsp
d7f86bbab Stagefright: Do not skip frames in time-lapse-source for high-speed
7b6310166 MediaProfiles: Enhance profiles for extended usecases
5b6b58970 av: compilation fix
b31d0ec70 libstagefright: use 64-bit usage for native_window_set_usage
db4b70c62 libstagefright: Free buffers on observer died
326035901 stagefright: ACodec: Resolve empty vendor parameters usage
====================
11-04-2019
====================
* frameworks/av/
0e772c177 libstagefright: Support YVU420SemiPlanar camera format
462d97547 MTP: Fix crash when no storages are available
fa0400edd nuplayer: Avoid crash when codec fails to load
====================
11-03-2019
====================
* device/generic/common/
8c644b2 Fix superuser prefix
f093fea Add addon call
* vendor/x86/
1a8de5b Add houdini addons
Thanks, and #stayblissful
Malik Munam said:
Hi, What is the secret code please send me at
[email protected]
Click to expand...
Click to collapse
That's not how this is going to work
My first impressions using 12.1 on my SURFACE PRO 1 tablet.
It runs smoothly - I'm very impressed with it. That loading screen artwork is very cool.
- At the lockscreen a message pops up saying "ANDROID SYSTEM" "There's an internal problem with your device. Contact your manufacturer for details"
- There are a lot of characters missing in text. For example, when I input the account name to my google account in Play Store some of the characters don't visually show up in the text input box - a blank space is there instead. The login still works though. Sometimes the missing characters glitch and show up for a second, then disappear again. Another example is when I'm browsing google search results with the built-in browser, some of the text on the search descriptions have blank space instead of characters. The text on the hyperlinks seems to be displayed correctly.
- The volume control hardware buttons do work, but the overall volume of the device is very low, even when turned up to maximum.
- Watching videos from within Firefox and the built-in internet browser does not work. It looks as though it's trying to load the video endlessly.
This is the first Bliss-OS release which allows files to be downloaded/stored onto my Surface Pro 1. The other release that worked with my Surface Pro 1 (Kernel 4.20) would not download/store files. This is the only other release (apart from Kernel 4.20) which works at all with my Surface Pro 1.
I'll let you know what else I encounter.
A couple more things I've noticed...
-The WIFI signal strength indicator always indicates there is zero WIFI strength, despite the WIFI working fine.
-The icons on the taskbar show through at the very bottom of the screen in one situation. Here's how to replicate the problem: open a game/app, then click the "windows" button on the Surface Pro, then go back into the game/app and the taskbar icons will show through slightly at the bottom of the screen.
-The volume (I mentioned in my previous post) is fine for installed apps, it seems to be low for only the internet browsers (built-in & Firefox).
electrikjesus said:
That's not how this is going to work
Click to expand...
Click to collapse
Yeah ! Lazy people should atleast use google ,its all over public link
I'm having problem when running it on old PC with ~2011 specs....
I only boot the shell and type logcat, it shows that "something....... tombstone.....something", will pull the log soon so you can see what's the problem