[ROM][DEV] Porting Halium to Galaxy S6

[ROM][DEV] Porting Halium to Galaxy S6 - Galaxy S6 General

In the interest of bringing convergence of linux operating system in phones and desktops after canonical abandoned the project, the halium.org project and ubports took the baton. Halium project's objective is to create a standard way to wrap all the android code necessary for a OS to talk to hardware so one can build a linux operating system on top of android (no java code getting in the way). It could be used by any number of OS's like sailfish, ubuntu touch or new mobile distributions, like archlinux on the phone (yeah, I'm an arch guy). It is based on the hybris library, whitch is kind of a wrap so the glibc can be interface with android libc (called bionic, which is a little bit off standard).
A lot of you know all that (specially the ones likely to help), I just giving some contest in case someone it's not tunned in.
So I'm on the endevour of porting it to galaxy S6 taking advantage of the work of TeamNexus (which is a working in progress), whom work on the device specific code made it possible to undertake this task and LinageOS for the rest of android code (Thank you both!).
So, for anyone who wants to coordinate efforts to make this port, or for anyone who wants to help me troubleshoot some of the problems I'm having, fell free to come aboard. Here are useful links:
Halium.org - Project homepage
porting documentation
TeamNexus git repository
Local Manifests: device code and repo manifest.
Here is a patch on all the modifications I had to do to so the device specific code
fixup-mountpost for the zerofltexx device (It is used to modify the fstab file so systemd can mount it without udev) apperantly there might be a format error on my part here. That is what the devs said, but I can't figure it out. I followed the instructions in the documentation... (I didn't wanted to push it with questions.)
progress so far:
- [x] Manifest with kernel, vendor, device tree
- [x] Setup kernel defconfig for hybris-boot (using mer-kernel scripts and zerofltexx kernel as reference)
- [x] Fix mountpoints
- [p] Build
- - [x] systemimage
- - [x] mkbootimg
- - [ ] hybris-boot
- [ ] Flash and test with reference rootfs
- - [ ] Get LXC working
- - [ ] Get wifi working
- - [ ] Halium tests
-- - [ ] test_vibrate
-- - [ ] test_lights
-- - [ ] test_vibrate
-- - [ ] test_hwcomposer
-- - [ ] test_audio
-- - [ ] test_camera
- - [ ] Clean up and share my manifest and sources and stuff
Testing rootfs:
- [ ] halium 7.1 reference
- [ ] Plasma Mobile (boots! Graphics! Wifi!)
- [ ] UBports rootfs
This first post is going to be updated with any information needed for porting Halium for galaxy s6 from source and its progress.
I will post the problems I had in another post, but I got to get going now. So I will just post the make error I'm getting

Hello Alkis05,
We are 2 young developers and we are interested in porting Ubuntu Touch for a Samsung device (Galaxy Tab A6 2016 10.1” : gtaxllte).
We were very excited to see that you are interested too in this project and, even if you are not porting it for the same device, we would be very happy to get in touch with you for this project.
We saw that you are at a quite advanced step of the project. As for us, we are trying to write the correct manifest in order to build Halium. We have lots of difficulties with this file because I don’t know how to include the correct repositories.
We would be very thankful if you could help us with this step, as we saw that you successfully did it for your device.
Would you be able to help us ?
As for the for the steps of the project, we would be very happy to participate. Would you accept to work with us on this project ?
Of course, we would continue the port on the two devices, yours and ours.
Finally, we would like to present ourselves :
We are two young teenagers : Nyell Xade Jean (15 years old, St Lucia) and Jean-Baptiste Amade (16 years old, France). We are very good friends and we have been working on lots of projects together.
Xade is a specialist of android devices, he has a dedicated YouTube channel about this subject (Pops Productions Tech).
As for me (Jb), I’m very interested in Linux (I’m using Ubuntu every day) and that’s why i decided to port Ubuntu Touch to my tablet.
Concerning the device we are working on, it’s a Samsung Galaxy Tab A6 2016 10.1” (manufacturer code name : gtaxllte). On GitHub I found different repositories related to this device but the difficulty I’m facing is that I can’t fill correctly the Halium manifest.
If you accept to help us, I’ll explain you more precisely my problem.
We hope that you’ll accept to work with us on this project.
Thank you in advance
Xade(@pops) and Jb
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
Hello Alkis05,
We are 2 young developers and we are interested in porting Ubuntu Touch for a Samsung device (Galaxy Tab A6 2016 10.1” : gtaxllte).
We were very excited to see that you are interested too in this project and, even if you are not porting it for the same device, we would be very happy to get in touch with you for this project.
We saw that you are at a quite advanced step of the project. As for us, we are trying to write the correct manifest in order to build Halium. We have lots of difficulties with this file because I don’t know how to include the correct repositories.
We would be very thankful if you could help us with this step, as we saw that you successfully did it for your device.
Would you be able to help us ?
As for the for the steps of the project, we would be very happy to participate. Would you accept to work with us on this project ?
Of course, we would continue the port on the two devices, yours and ours.
Finally, we would like to present ourselves :
We are two young teenagers : Nyell Xade Jean (15 years old, St Lucia) and Jean-Baptiste Amade (16 years old, France). We are very good friends and we have been working on lots of projects together.
Xade is a specialist of android devices, he has a dedicated YouTube channel about this subject (Pops Productions Tech).
As for me (Jb), I’m very interested in Linux (I’m using Ubuntu every day) and that’s why i decided to port Ubuntu Touch to my tablet.
Concerning the device we are working on, it’s a Samsung Galaxy Tab A6 2016 10.1” (manufacturer code name : gtaxllte). On GitHub I found different repositories related to this device but the difficulty I’m facing is that I can’t fill correctly the Halium manifest.
If you accept to help us, I’ll explain you more precisely my problem.
We hope that you’ll accept to work with us on this project.
Thank you in advance
Xade(@pops) and Jb

fixup-mountpoints file
Looks like your fixup-mountpoints entry need to be adjusted a little bit. It needs to be like this (like the entries already in that file):
Code:
"zerofltexx")
sed -i \
-e 's block/platform/15570000.ufs/by-name/SYSTEM sda15 ' \
-e 's block/platform/15570000.ufs/by-name/EFS sda3 ' \
-e 's block/platform/15570000.ufs/by-name/CACHE sda16 ' \
-e 's block/platform/15570000.ufs/by-name/USERDATA sda18 ' \
-e 's block/platform/15570000.ufs/by-name/PERSISTENT sda11 ' \
-e 's block/platform/15570000.ufs/by-name/HIDDEN sda17 ' \
"[email protected]"
;;

any update? I want to give it a try

Related

Source code OMX ST-Ericsson

Hi, I found in the Galaxy S Advance Forum have posted a zip file containing source code OMX ST-Ericsson on Xperia U's Android Development Thread named "[ROM] [NIGHTLY] [TeamCanjica][UB] Unofficial CyanogenMod 10.1". No way around it but here is the download link for developers who are interested in this mediafire.com/download/hzg68480ecjozpy/vendor.zip

pabloo.b said:
Hi, I found in the Galaxy S Advance Forum have posted a zip file containing source code OMX ST-Ericsson on Xperia U's Android Development Thread named "[ROM] [NIGHTLY] [TeamCanjica][UB] Unofficial CyanogenMod 10.1". No way around it but here is the download link for developers who are interested in this mediafire.com/download/hzg68480ecjozpy/vendor.zip
Click to expand...
Click to collapse
That source look quite nice. There isn`t any binary elements and even have some documentation.

MateuszKrawczuk said:
That source look quite nice. There isn`t any binary elements and even have some documentation.
Click to expand...
Click to collapse
and you know if someone could prove or see if any of this serve?

pabloo.b said:
and you know if someone could prove or see if any of this serve?
Click to expand...
Click to collapse
there are 2 main folders, connectivity and multimedia
in connectivity we have something related to wlan
in multimedia we have a some files to generate the code and some documentatation
i dont think this is the NovaThor U8420
as far as i know the u8420 is a clone of the u8500 made specific for the s3 mini, some users where able to flash the xperia u kernel with overclock to 1.15>Ghz with afew side effects...
this is what is written in th readme of the "kernel"
note the date is from 2009
Bellagio OpenMAX Integration Layer 1.1.2 project
Release 0.9.2.1
This is an Open Source implementation of the OpenMAX Integration Layer
(IL) API ver. 1.1.2, specified by the Khronos group (see
http://www.khronos.org/openmax).
This package includes the libomxil-bellagio shared library together with the
following OpenMAX components (built as separate shared objects and
loaded at runtime):
CORE FUNCTIONALITIES
- An IL core
- A component loader for static libraries for Linux
- A simple resource manager
- A framework of components and ports base classes for Bellagio Hierarchy
- a draft support to content pipes
AUDIO
- OMX audio volume control
- OMX audio mixer component
VIDEO
- a video scheduler connected to a clock component for video synchronization
CLOCK
- OMX Clock component. It take audio(default) as input reference clock
and provide media clock to video sink and other component. It support
fast forward and rewind.
=============================
IMPORTANT NOTE
=============================
All the other components present in the old versions of Bellagio
are distributed from the 0.9.2 on as external packages maintained separately.
If you need more details you can check the download page in the Bellagio web site:
http://omxil.sourceforge.net/downloads.html
=============================
BUILD the bellagio library
=============================
autoreconf -i -f $(source_path)
$(source_path)/configure
make
make install
make check
Before attempting to run any test, the OMX components *must* be
registered with the command "omxregister-bellagio".
omxregister-bellagio components_path1:components_path2
That will create a registry file that will contain all the components
installed in the specified directories. By default the components
distributed with this package are installed in /usr/local/lib/bellagio
and the registry entries are stored in the file $HOME/.omxregister
The location of registry file can be changed setting the environment variable
OMX_BELLAGIO_REGISTRY to the location and name of the new register file.
Note: the default location for the installation is TARGET=/usr/local/lib
for the library, and the component will be installed in TARGET/bellagio
To change the installation directory execute the configure as in the example:
$(source_path)/configure --prefix=new_installation_path
=============================
TEST
=============================
The following simple test applications are provided:
test/components/audio_effects/omxvolcontroltest
test/components/audio_effects/omxaudiomixertest
test/components/resource_manager/omxrmtest
TEST USAGE
----------------------------------------------
Usage: omxvolcontroltest [-o outfile] [-g gain] filename
-o outfile: If this option is specified, the output stream is
written to outfile otherwise redirected to std
output
-g: Gain of PCM data [0...100]
-h: Displays this help
Usage: omxaudiomixertest [-o outfile] [-gi gain] -t -r 44100 -n 2 filename1 filename2 [filename3] [filename4]
-o outfile: If this option is specified, the output stream is
written to outfile otherwise redirected to std
output; Can't be used with -t.
-gi : Gain of stream i[0..3] data [0...100]
-t : The audio mixer is tunneled with the ALSA sink;
Can't be used with -o
-r 44100 : Sample Rate [Default 44100]
-n 2 : Number of channel [Default 2]
-h : Displays this help
The omxvolcontroltest and omxaudiomixertest receive as input an audio decompressed stream.
If an output file is produced yet another uncompressed audio stream is written.
The purpose of these tests is to verify the correct behavior of audio effects volume control ands audio mixer.
If any developer is interested in a full multimedia chain with codecs also please refer to the external components
and relates tests. A set of application using many components is also provided as a separate package.
For further details go to the download page of the Bellagio web pages:
http://omxil.sourceforge.net/downloads.html
=============================
BUILD RPM
=============================
- To build RPM:
make dist
cp libomxil-bellagio-0.9.2.tar.gz $HOME/rpmbuild/SOURCES/
rpmbuild -bb libomxil-bellagio.spec
=============================
BUILD DEB
=============================
To build the installable deb package with the Bellagio libraries run:
sudo checkinstall --pkgsource=/home/urlinigi/OpenMAX/sourceforge/omxil --install=no [email protected] --spec=/home/urlinigi/OpenMAX/sourceforge/omxil/libomxil-bellagio.spec --inspect
=============================
SOURCE CODE PACKAGE
=============================
There are two ways to generate the source code package. One is provided by the
makefile internal structure, running the following command:
make dist
In Ubuntu system is also available the debian mechanism to build a
source code package, running the following instructions, in the base
directory of the source code:
dpkg-buildpackage -S
=============================
DITRIBUTIONS
=============================
This version has been tested on:
- UBUNTU 9.10
- Fedora Core 11
Last modified: Dec 23, 2009
Click to expand...
Click to collapse

From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think

tys0n said:
From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think
Click to expand...
Click to collapse
Where did you read it?
Sent from my GT-I8190 using Tapatalk 4

tys0n said:
From what I've read, the only difference between NovaThor U8500 and U8420 is the Thor (modem-part).
U8420 doesn't have the HSPA+ modem. Other than that it's the same...I think
Click to expand...
Click to collapse
ppero196 said:
Where did you read it?
Sent from my GT-I8190 using Tapatalk 4
Click to expand...
Click to collapse
I can't remember where it was and I can't find it now. Somwhere I read that U8420 is a scaled down U8500 and that is was the modem that was scaled down. When looking at the specs it all made sense but I can't be 100% sure.

We have Bellagio sources from a few months Even Samsung published them
What is Bellagio?
OMX on our phone are from Symbian (yes, the same Symbian which you could have ealier on your Nokia). Bellagio is wrapper to use OMX from Symbian on Android. It's available on GPL license, so STE/Samsung has to publish its sources.

New Macław said:
We have Bellagio sources from a few months Even Samsung published them
What is Bellagio?
OMX on our phone are from Symbian (yes, the same Symbian which you could have ealier on your Nokia). Bellagio is wrapper to use OMX from Symbian on Android. It's available on GPL license, so STE/Samsung has to publish its sources.
Click to expand...
Click to collapse
wonderful!!

[Devs] Looking for a kernel base to work with? Start here.

Hello!
I'm hoping to get custom kernel & rom development up and running quickly for the G5 community, and have created a git repository which provides a kernel source base to start with.
What I've done is taken the v10a release sources and modified them to work with build directories and multiple variants. (should they be unlocked or receive the CodeFire treatment at any time)
Here's where to start: https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0
If you'd like a somewhat updated kernel, the stock-6.0.y branch will be patched from Linux 3.18.y branch at kernel.org, see:
https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0.y
Different from the absolute stock defconfigs, I've made the following changes:
Module signature verification disabled
Unnecessary debugging flags separated into debug_defconfig (use EXTRA_DEFCONFIG=debug_defconfig to enable them)
Flags that were previous set to module (=m) have been set to =y (built-in) in case incompatibilities are unable to load stock modules
Each known variant & target is listed in build.sh comments. The default variant when building with ./build.sh is h850 with debugging disabled.
When using the Makefile, VARIANT_DEFCONFIG=variant_xxx_defconfig adds the additional settings per variant to the target defconfig. (by default stock_defconfig)
build.sh is set up to automatically build a dtb.img after creating the kernel Image.gz based on whichever variant you've built for.
You can use ./menuconfig.sh to modify the stock defconfig, or you can copy the stock_defconfig to another name such as my_defconfig and use TARGET=my ./menuconfig or TARGET=my ./build.sh
It's easier to just set the default target in build.sh/menuconfig.sh - each have their configuration options near the top of the files.
Be sure to edit the config variables in build.sh and menuconfig.sh before using. The VERSION file gets appended to the kernel version shown in `uname` when using build.sh.
The toolchain must be pointed to the correct location before it can build. Be sure to have libncurses5-dev and colordiff packages installed for menuconfig.sh.
For a toolchain, I recommend using the GCC Linaro aarch64 5.3 2016.02 release. You can use basically any aarch64 toolchain though.
Download here: https://releases.linaro.org/compone...o-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz
You can start by forking my repository on GitHub and giving it your own name if you like. Extra interesting commits are available in the other branches that you should be able to cherry-pick without issues should you be interested in them.
Looking to test your kernel Image.gz + dtb.img?
Look no further than my LazyFlasher repository!
See here: https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
Simply do:
Code:
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git kernel-flasher
cd kernel-flasher
cp /path/to/Image.gz /path/to/dtb.img ./
make
(simply place your kernel Image.gz (optional) and dtb.img (optional) in the root of the repository and type make!)
And you'll have your own dynamic kernel flashing zip for custom recoveries!
The kernel-flasher repository is capable of great things. You can create scripts in patch.d to do anything you like.
Add files to the ramdisk-patch folder and create a script that copies them into the $ramdisk folder and they will be rebuilt into the ramdisk!
By default, no-verity-opt-encrypt is there as an example.
Using setprop in patch.d scripts allows you to set props in default.prop with ease.
Add functions to patch.d-env to make them globally usable across patch.d scripts.
See other branches for more examples, like how to add f2fs lines to the fstab, or patch for system mode SuperSU.
LazyFlasher is the installer used in the Kali NetHunter project. You can also find more examples in the kali-nethunter GitHub!
Good luck, and happy kernel developing!

Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?

toefurkey said:
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
Click to expand...
Click to collapse
I'm a little tired and somewhat intoxicated here at 3:45 AM so this is going to be a bit of rambling and so on...
While it's certainly a good idea to study up on what interests you before digging into it, sometimes it really can be easier just to dive in to your hobby.
I'm a high school drop out, never made it through college. Everything I've learned is by taking the great work done by the open source community and reading their code and applying it to other projects. That's the great thing about open source and nonrestrictive licenses. Everything is there for you to figure out, make changes, borrow code, run into problems, and the best part - search for solutions that others have already provided in their struggle to do exactly what you're doing.
Have an idea for a great feature? You can probably find it already implemented in another kernel somewhere.
Find the work someone else has done and modify it to fit your needs, but don't forget to give them credit for their work that you've used!
If you're going to start writing your own code, be certain to keep it tidy and variables/functions with meaningful names and comments so that not only others can understand and learn from it, but that you can return to the same code later on and understand it. Confusing code is how bugs tend to show up and become almost impossible to squash.
What I'm trying to get across here is don't be afraid to not be original. Don't be afraid to use others work to accomplish what you want, so long as they receive some attribution. The quickest way to learn how things work is by understanding what's already there and available to you.
You'll notice that there's projects all over XDA with special features ported from one device to another. Isn't it great having the all the best features people have added to other devices on one really nice device that you have?
PS I've never been on the XDA-U site before, so I can't give an opinion there.
I forgot what I was on about so I'll end this here lol.

?jcadduono you're on fire man thank you for everything you've been doing so far with such little resources.
Sent from my LG-H820 using XDA-Developers mobile app

jcadduono, thanks for the info and wonderful words of wisdom!
I totally agree on what you're saying and my goal is to try diving into this as a hobby. The hardest part for me isn't so much the coding part, but just figuring out a starting point to get grounded and build upon and I feel like what you've provided here is perhaps the starting point I need. Now it's just up to me to push myself in my free time.

Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.

Pinu'u said:
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Click to expand...
Click to collapse
Hopefully once the toolchain path is set you should only need to run ./build.sh to actually build the kernel and dtb.
You may be missing some items for menuconfig.sh, which should just be solved by apt-get install colordiff libncurses5-dev
If building inside a ROM tree, it should be fairly simple for developers to adjust their ROM configs to add more to the kernel make command line, such as VARIANT_DEFCONFIG.

No matter what i do, kernel builds, but no dtb.img will be created. Any ideas where to look / what to test ?
I have stock-6.0.y, and did the h850 one.

Hi, is the stock-6.0.y branch removed?
I didnt find it. and need the right defconfig
greetz
mericon

[WIP] [Help wanted] Making postmarketOS Linux port

Hey everyone!
So inspired by the Ubuntu thread, I decided to tackle making a port of postmarketOS, a version of Alpine Linux designed to run on legacy smartphones.
The progress is going pretty well, the device boots, the display works and you can log in via ssh. What doesn't work yet is Wifi and the kernel complains about several issues with CPU frequency drivers and then panics after a few minutes.
It'd be great if someone who knows more than I do could build the OS themselves and try to debug the kernel and upload patches or suggest a troubleshooting path.
Sources are here: https://github.com/postmarketos/pmbootstrap
Additional info on porting: https://wiki.postmarketos.org/wiki/Porting_to_a_new_device

Good to see some more interest in this. I'm far from being any help coding/building but will keep following to help test. My tablet has just been sitting lately anyway.

The pull request actually got approved. The initial device config is now in the official repo, waiting to be improved upon. Updated the link to point to the postmarketos github.

@flar2 @USBhost
If you're not too busy or bored by this project, it'd be neat of you could have a look at the current issue we're having. You're more experienced with kernels than I am, derp:
https://github.com/postmarketOS/pmbootstrap/issues/1384

Alexandroid99 said:
@flar2 @USBhost
If you're not too busy or bored by this project, it'd be neat of you could have a look at the current issue we're having. You're more experienced with kernels than I am, derp:
https://github.com/postmarketOS/pmbootstrap/issues/1384
Click to expand...
Click to collapse
Any kernel logs ?
It could be that the kernel was configured wrong. Or bad toolchain.

There's a dmesg posted on the issue.

Alexandroid99 said:
There's a dmesg posted on the issue.
Click to expand...
Click to collapse
Let's pretend that never happened :angel:
Edit: @Alexandroid99 I think I know what happened... Disable hung task in the config.
If you still have problems I will look through the whole config in the morning.

USBhost said:
Let's pretend that never happened :angel:
Click to expand...
Click to collapse
No worries. I'm glad enough that you're taking time to look at it anyway. From what I can gather, it's failing to control the CPU and fails to find firmware, even though I'm using kernel params and the correct wifi fw path in the kernel config.

USBhost said:
Let's pretend that never happened :angel:
Edit: @Alexandroid99 I think I know what happened... Disable hung task in the config.
If you still have problems I will look through the whole config in the morning.
Click to expand...
Click to collapse
Ooo that does sound helpful for further debugging at the very least. Thanks!

Alexandroid99 said:
Ooo that does sound helpful for further debugging at the very least. Thanks!
Click to expand...
Click to collapse
Does it still crash?

USBhost said:
Does it still crash?
Click to expand...
Click to collapse
Sadly, yes. Dmesg is still complaining about the firmware issues even when /vendor is mounted & the firmware is automatically copied to the initfs ramdisk at startup to /lib/firmware, plus we get these strange errors about the cpu frequency not being controllable. It does seem to run a tiny bit longer, so I could pipe a very late dmesg output to a file and pull it from the device. Gist here: https://gist.github.com/Alexandroid99/21fd1dafa931421d87c16d784ec6068d
Defconfig:
https://github.com/postmarketOS/pmb...inux-htc-flounder/config-htc-flounder.aarch64
At this point I'm not sure if it's related to the kernel not finding its firmware or if it's related to the modifications the distro makes. At least it kind of does boot, which is an advantage over other devices that don't even make it to userland.
Thanks for taking time, I appreciate you helping. ^_^

Alexandroid99 said:
Hey everyone!
So inspired by the Ubuntu thread, I decided to tackle making a port of postmarketOS, a version of Alpine Linux designed to run on legacy smartphones.
The progress is going pretty well, the device boots, the display works and you can log in via ssh. What doesn't work yet is Wifi and the kernel complains about several issues with CPU frequency drivers and then panics after a few minutes.
It'd be great if someone who knows more than I do could build the OS themselves and try to debug the kernel and upload patches or suggest a troubleshooting path.
Sources are here: https://github.com/postmarketos/pmbootstrap
Additional info on porting: https://wiki.postmarketos.org/wiki/Porting_to_a_new_device
Click to expand...
Click to collapse
WHoooaa wow, This is great to here, as I plan on tackling Sailfish OS on flounder after it comes in the mail (still working on manta Nexus 10 audio issues >:c ). Any special configs you had to set with the kernel? I assume PostMarket OS uses Hybris or something similar for HW adaptation

Galaxyninja66 said:
WHoooaa wow, This is great to here, as I plan on tackling Sailfish OS on flounder after it comes in the mail (still working on manta Nexus 10 audio issues >:c ). Any special configs you had to set with the kernel? I assume PostMarket OS uses Hybris or something similar for HW adaptation
Click to expand...
Click to collapse
Ehm we're nowhere near hwaccel yet and I've posted different versions of the defconfig before. The most recent is already in the official repo. All we have is a more or less booting device with a cyan cursor (if Mate desktop is installed) that crashes after three minutes. Look around the pmbootstrap repo and wiki for more info. And the devs said they haven't packaged libhybris for the Alpine Linux base yet, so that's still no-go.

@Alexandroid99 What CM/LOS base are you using? CM12.1? LOS14.1???
---------- Post added at 03:44 AM ---------- Previous post was at 03:05 AM ----------
Alexandroid99 said:
Ehm we're nowhere near hwaccel yet and I've posted different versions of the defconfig before. The most recent is already in the official repo. All we have is a more or less booting device with a cyan cursor (if Mate desktop is installed) that crashes after three minutes. Look around the pmbootstrap repo and wiki for more info. And the devs said they haven't packaged libhybris for the Alpine Linux base yet, so that's still no-go.
Click to expand...
Click to collapse
If you can, spam dmesg in terminal until it crashes, or, if possible, telnet into the device (maybe postmarket doesn't have telnet, I don't know) and run dmesg, and figure out what process is causing the crash.

Galaxyninja66 said:
@Alexandroid99 What CM/LOS base are you using? CM12.1? LOS14.1???
---------- Post added at 03:44 AM ---------- Previous post was at 03:05 AM ----------
If you can, spam dmesg in terminal until it crashes, or, if possible, telnet into the device (maybe postmarket doesn't have telnet, I don't know) and run dmesg, and figure out what process is causing the crash.
Click to expand...
Click to collapse
Base is LOS-15.1 branch.
And pmos has got ssh built in and I've already spammed dmesg, that's how I got that dmesg gist.

Alexandroid99 said:
Base is LOS-15.1 branch.
And pmos has got ssh built in and I've already spammed dmesg, that's how I got that dmesg gist.
Click to expand...
Click to collapse
Guess I'll need to wait for Hybris-15.1 for sailfish os : ( oh well;

Galaxyninja66 said:
Guess I'll need to wait for Hybris-15.1 for sailfish os : ( oh well;
Click to expand...
Click to collapse
Who cares about libhybris when we don't have a stable kernel yet? FYI the tegra vendor libs stopped being updated during the times of 7.1.2; they don't have to do anything with Lineage 15.1. The kernel itself is from the 15.1 branch because that's the version receiving updates right now afaik and not that different from 14.1 (I think).
The Ubuntu port is stable enough to run even though it doesn't use libhybris for anything, at least it wasn't mentioned. I appreciate your interest, but kindly have a look at the dmesg gist and tinker around with the builds if you've got an idea, or just leave it be. All we need right now is debug the kworker hang that occurs after about three minutes of uptime and is probably at least partially caused by missing firmware. There's of stuff you can do while forking:
- try to install firmware into the initramfs and see if that helps
- Add an initramfs hook and fstab entry to mount /vendor
- Make a new kernel defconfig with fixes if you think there's an error in there
- Make a new kernel package based on different lineage branches just to be sure
So, fork the pmbootstrap repo and get to it and forget about libhybris and next time read my posts better, because you suggested making a dmesg log when I had already mentioned that I managed to pull a very late dmesg aaand you could have found out the kernel base by yourself by looking at the repo on github.

@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Code:
WARNING: at drivers/platform/tegra/../../../arch/arm/mach-tegra/tegra12_clocks.c:1585 tegra12_cpu_clk_set_rate+0x16c/0x4b0()
[ 1.450449] Increasing CPU rate while regulator is not ready is not allowed
[ 1.450463] Modules linked in:
[ 1.450497] CPU: 1 PID: 48 Comm: cfinteractive Tainted: G W 3.10.103-pmos #1-postmarketOS
[ 1.450518] Call trace:
[ 1.450546] [<ffffffc000089508>] dump_backtrace+0x0/0x150
[ 1.450570] [<ffffffc00008966c>] show_stack+0x14/0x20
[ 1.450626] [<ffffffc000ae8ce8>] dump_stack+0x20/0x28
[ 1.450648] [<ffffffc0000ac1b0>] warn_slowpath_common+0x78/0xa0
[ 1.450669] [<ffffffc0000ac218>] warn_slowpath_fmt+0x40/0x48
[ 1.450688] [<ffffffc000832674>] tegra12_cpu_clk_set_rate+0x16c/0x4b0
[ 1.450709] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450729] [<ffffffc00082a070>] tegra12_cpu_cmplx_clk_set_rate+0x48/0xd8
[ 1.450748] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450766] [<ffffffc000828bd0>] clk_set_rate+0x58/0x230
[ 1.450787] [<ffffffc00083e028>] tegra_update_cpu_speed+0x180/0x3d8
[ 1.450806] [<ffffffc00083e75c>] tegra_cpu_set_speed_cap_locked+0x8c/0x100
[ 1.450824] [<ffffffc00083ee4c>] tegra_target+0x7c/0xa8
[ 1.450845] [<ffffffc0007acc8c>] __cpufreq_driver_target+0xa4/0x368
[ 1.450867] [<ffffffc0007b69bc>] cpufreq_interactive_speedchange_task+0x174/0x258
[ 1.450888] [<ffffffc0000d8fc8>] kthread+0xd0/0xd8
[ 1.450903] ---[ end trace 1b75b31a2719ed1f ]---
[ 1.450919] cpu-tegra: Failed to set cpu frequency to 714000 kHz

Alexandroid99 said:
@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Code:
WARNING: at drivers/platform/tegra/../../../arch/arm/mach-tegra/tegra12_clocks.c:1585 tegra12_cpu_clk_set_rate+0x16c/0x4b0()
[ 1.450449] Increasing CPU rate while regulator is not ready is not allowed
[ 1.450463] Modules linked in:
[ 1.450497] CPU: 1 PID: 48 Comm: cfinteractive Tainted: G W 3.10.103-pmos #1-postmarketOS
[ 1.450518] Call trace:
[ 1.450546] [<ffffffc000089508>] dump_backtrace+0x0/0x150
[ 1.450570] [<ffffffc00008966c>] show_stack+0x14/0x20
[ 1.450626] [<ffffffc000ae8ce8>] dump_stack+0x20/0x28
[ 1.450648] [<ffffffc0000ac1b0>] warn_slowpath_common+0x78/0xa0
[ 1.450669] [<ffffffc0000ac218>] warn_slowpath_fmt+0x40/0x48
[ 1.450688] [<ffffffc000832674>] tegra12_cpu_clk_set_rate+0x16c/0x4b0
[ 1.450709] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450729] [<ffffffc00082a070>] tegra12_cpu_cmplx_clk_set_rate+0x48/0xd8
[ 1.450748] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450766] [<ffffffc000828bd0>] clk_set_rate+0x58/0x230
[ 1.450787] [<ffffffc00083e028>] tegra_update_cpu_speed+0x180/0x3d8
[ 1.450806] [<ffffffc00083e75c>] tegra_cpu_set_speed_cap_locked+0x8c/0x100
[ 1.450824] [<ffffffc00083ee4c>] tegra_target+0x7c/0xa8
[ 1.450845] [<ffffffc0007acc8c>] __cpufreq_driver_target+0xa4/0x368
[ 1.450867] [<ffffffc0007b69bc>] cpufreq_interactive_speedchange_task+0x174/0x258
[ 1.450888] [<ffffffc0000d8fc8>] kthread+0xd0/0xd8
[ 1.450903] ---[ end trace 1b75b31a2719ed1f ]---
[ 1.450919] cpu-tegra: Failed to set cpu frequency to 714000 kHz
Click to expand...
Click to collapse
Yo... I'll look into it. And yes I am.

USBhost said:
@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Yo... I'll look into it. And yes I am.
Click to expand...
Click to collapse
Alrighty, cheers! Are you doing builds yourself to debug or should I keep on feeding you kernel logs whenever you require some? Thanks!

Bliss OS - Pie for PCs (LTS)

The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates

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-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
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)
-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.
Q: OK, So I have a BlahBlah 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:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.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.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie 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...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io

Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.

Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!

AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon

Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.

Does not work on Asus t101ha (cherrytrail)

wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.

vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable

electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk

AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.

Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.

mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?

electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.

electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.

mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install

Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks

Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower

Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?

Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds

{
"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

Database Users

welcome