Discussion:
Bliss-x86 - Custom ROM for Android-x86
(too old to reply)
Jon West
2017-01-11 16:39:07 UTC
Permalink
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.

Enough banter, here's the
link: https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Andrew Matthews
2017-01-12 08:16:56 UTC
Permalink
OMG!!! Thanks what about the Acer Swtich 10 one? But OMG!!!!
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Andrew Matthews
2017-01-12 08:20:37 UTC
Permalink
But keep up the good work :)
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Andrew Matthews
2017-01-12 08:33:13 UTC
Permalink
So on my Acer Switch 10 One: Touchscreen does not work, wifi, sdcard or
sound but it is a new Tablet, I love this rom
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
오영민
2017-01-12 12:58:32 UTC
Permalink
It's really cool! but..

Are you planning to release 4.8 or 4.9 kernel?
Some models of the surface will work with the touch screen version of the
4.8 kernel or higher.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-12 13:53:42 UTC
Permalink
I should have those drives and patches added in this kernel. Have you tried
it on one of the newer Surfaces? I do have a plan to use kernel-4.10, and
mesa 13.x but I keep hitting a brick wall when trying to build with what
maurossi has on his github
Post by 오영민
It's really cool! but..
Are you planning to release 4.8 or 4.9 kernel?
Some models of the surface will work with the touch screen version of the
4.8 kernel or higher.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-12 15:19:35 UTC
Permalink
I should have those drivers and patches added in this kernel. Have you
tried it on one of the newer Surfaces? I do have a plan to use kernel-4.10,
and mesa 13.x but I keep hitting a brick wall when trying to build with
what maurossi has on his github
Post by 오영민
It's really cool! but..
Are you planning to release 4.8 or 4.9 kernel?
Some models of the surface will work with the touch screen version of the
4.8 kernel or higher.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-12 19:09:28 UTC
Permalink
Thanks for the work on this. Am using the 6.4 32bit iso and it's working
well. Had a few problems just after install, mostly with dpi and the
launcher. Going to try out 7.1.1 shortly just to play around with it.
Carefully considering whether or not to use one of these as a daily driver.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-01-13 16:41:14 UTC
Permalink
debug mode


<13>[ 23.566386] init: Service 'daemonsu' (pid 1700) killing any children
in process group
<13>[ 28.610058] init: Service 'daemonsu' (pid 1712) killing any children
in process group
<13>[ 33.653818] init: Service 'daemonsu' (pid 1720) killing any children
in process group
<13>[ 33.994177] init: Service 'zygote' (pid 1425) killed by signal 6
<13>[ 34.013834] init: Service 'zygote' (pid 1425) killing any children
in process group
<13>[ 34.072821] init: Service 'audioserver' is being killed...
<13>[ 34.091384] init: Service 'cameraserver' is being killed...
<13>[ 34.110161] init: Service 'media' is being killed...
<13>[ 43.220881] init: Service 'daemonsu' (pid 1975) killing any children
in process group
<13>[ 43.559129] init: Service 'zygote' (pid 1729) killed by signal 6
<13>[ 43.574930] init: Service 'zygote' (pid 1729) killing any children
in process group
<13>[ 43.621739] init: Service 'audioserver' is being killed...
<13>[ 43.637382] init: Service 'cameraserver' is being killed...
<13>[ 43.652606] init: Service 'media' is being killed...
<13>[ 48.691068] init: Service 'daemonsu' (pid 2220) killing any children
in process group
<13>[ 53.033834] init: Service 'zygote' (pid 1983) killed by signal 6
<13>[ 53.034018] init: Service 'zygote' (pid 1983) killing any children
in process group
<13>[ 53.034838] init: Service 'audioserver' is being killed...
<13>[ 53.036398] init: Service 'cameraserver' is being killed...
<13>[ 53.036628] init: Service 'media' is being killed...
<13>[ 54.065902] init: Service 'daemonsu' (pid 2326) killing any children
in process group
<13>[ 59.089615] init: Service 'daemonsu' (pid 2484) killing any children
in process group
<13>[ 62.468896] init: Service 'zygote' (pid 2235) killed by signal 6
<13>[ 62.507635] init: Service 'zygote' (pid 2235) killing any children
in process group
<13>[ 62.557397] init: Service 'audioserver' is being killed...
<13>[ 62.570438] init: Service 'cameraserver' is being killed...
<13>[ 62.583237] init: Service 'media' is being killed...
<13>[ 68.634607] init: Service 'daemonsu' (pid 2749) killing any children
in process group
<13>[ 72.067764] init: Service 'zygote' (pid 2498) killed by signal 6
<13>[ 72.080888] init: Service 'zygote' (pid 2498) killing any children
in process group
<13>[ 72.119057] init: Service 'audioserver' is being killed...
<13>[ 72.132922] init: Service 'cameraserver' is being killed...
<13>[ 72.135387] init: Service 'media' is being killed...
<13>[ 78.190386] init: Service 'daemonsu' (pid 3013) killing any children
in process group
<13>[ 81.747654] init: Service 'zygote' (pid 2764) killed by signal 6
<13>[ 81.747669] init: Service 'zygote' (pid 2764) killing any children
in process group
<13>[ 81.747839] init: Service 'audioserver' is being killed...
<13>[ 81.747978] init: Service 'cameraserver' is being killed...
<13>[ 81.748028] init: Service 'media' is being killed...
<13>[ 83.791809] init: Service 'daemonsu' (pid 3198) killing any children
in process group
<13>[ 88.860806] init: Service 'daemonsu' (pid 3272) killing any children
in process group
<13>[ 91.241791] init: Service 'zygote' (pid 3026) killed by signal 6
<13>[ 91.253039] init: Service 'zygote' (pid 3026) killing any children
in process group
<13>[ 91.288864] init: Service 'audioserver' is being killed...
<13>[ 91.300747] init: Service 'cameraserver' is being killed...
<13>[ 91.318568] init: Service 'media' is being killed...
<13>[ 98.391276] init: Service 'daemonsu' (pid 3527) killing any children
in process group
<13>[ 100.602113] init: Service 'zygote' (pid 3284) killed by signal 6
<13>[ 100.602132] init: Service 'zygote' (pid 3284) killing any children
in process group
<13>[ 100.602329] init: Service 'audioserver' is being killed...
<13>[ 100.602576] init: Service 'cameraserver' is being killed...
<13>[ 100.602636] init: Service 'media' is being killed...
<13>[ 103.653937] init: Service 'daemonsu' (pid 3775) killing any children
in process group
<13>[ 108.710070] init: Service 'daemonsu' (pid 3791) killing any children
in process group
<13>[ 110.466760] init: Service 'zygote' (pid 3540) killed by signal 6
<13>[ 110.477033] init: Service 'zygote' (pid 3540) killing any children
in process group
<13>[ 110.509219] init: Service 'audioserver' is being killed...
<13>[ 110.519696] init: Service 'cameraserver' is being killed...
<13>[ 110.529974] init: Service 'media' is being killed...
<13>[ 118.606055] init: Service 'daemonsu' (pid 4050) killing any children
in process group
<13>[ 119.849965] init: Service 'zygote' (pid 3800) killed by signal 6
<13>[ 119.859641] init: Service 'zygote' (pid 3800) killing any children
in process group
<13>[ 119.890091] init: Service 'audioserver' is being killed...
<13>[ 119.900785] init: Service 'cameraserver' is being killed...
<13>[ 119.911945] init: Service 'media' is being killed...
<13>[ 123.996813] init: Service 'daemonsu' (pid 4300) killing any children
in process group
<13>[ 129.085475] init: Service 'daemonsu' (pid 4322) killing any children
in process group
<13>[ 129.416848] init: Service 'zygote' (pid 4059) killed by signal 6
<13>[ 129.429324] init: Service 'zygote' (pid 4059) killing any children
in process group
<13>[ 129.429548] init: Service 'audioserver' is being killed...
<13>[ 129.431032] init: Service 'cameraserver' is being killed...
<13>[ 129.438972] init: Service 'media' is being killed...
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-13 18:25:10 UTC
Permalink
I am having the same problem with 7.1.1. It installs ok, but on first boot
never makes past the Android login command post screen.

6.4 runs well, except for the DPI problem[240dpi on a laptop? Seriously?]
which is easily solved[add ro.sf.lcd_denisty 160 to build.prop]
Debug stuff you posted
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-13 19:08:25 UTC
Permalink
Debug mode will not work properly in Bliss. Most end users will use the included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-01-13 19:10:50 UTC
Permalink
Alt+f1alt+f2alt+f3cd to rootfs
android terminal
x86:/ $ su
x86:/ # ash
/ # echo 0 0 0 0 > /proc/sys/kernel/printk
/ #

圚 2017幎1月14日星期六 UTC+8䞊午3:08:25Jon West写道
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-13 19:20:27 UTC
Permalink
Alt+f1alt+f2alt+f3cd to rootfs 
android terminal
x86:/ $ su
x86:/ # ash
/ # echo 0 0 0 0 > /proc/sys/kernel/printk
/ #
圚 2017幎1月14日星期六 UTC+8䞊午3:08:25Jon West写道Debug mode will not work properly in Bliss. Most end users will use the included Terminal and su. What do you need Debug mode for anyways?
It seems to be working on my end. Maybe I'm just confused as to what it is you need here...
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-01-13 19:22:47 UTC
Permalink
do you know Alt+f2Alt +f3 

圚 2017幎1月14日星期六 UTC+8䞊午3:20:28Jon West写道
Post by Jon West
Post by youling 257
Alt+f1alt+f2alt+f3cd to rootfs
android terminal
x86:/ $ su
x86:/ # ash
/ # echo 0 0 0 0 > /proc/sys/kernel/printk
/ #
圚 2017幎1月14日星期六 UTC+8䞊午3:08:25Jon West写道Debug mode will not work
properly in Bliss. Most end users will use the included Terminal and su.
What do you need Debug mode for anyways?
It seems to be working on my end. Maybe I'm just confused as to what it is you need here...
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-01-13 19:27:51 UTC
Permalink
alt+f2mount > /mnt/mount.txtcd /mnt/$SRC

圚 2017幎1月14日星期六 UTC+8䞊午3:22:47youling 257写道
Post by youling 257
do you know Alt+f2Alt +f3 
圚 2017幎1月14日星期六 UTC+8䞊午3:20:28Jon West写道
Post by Jon West
Post by youling 257
Alt+f1alt+f2alt+f3cd to rootfs
android terminal
x86:/ $ su
x86:/ # ash
/ # echo 0 0 0 0 > /proc/sys/kernel/printk
/ #
圚 2017幎1月14日星期六 UTC+8䞊午3:08:25Jon West写道Debug mode will not work
properly in Bliss. Most end users will use the included Terminal and su.
What do you need Debug mode for anyways?
It seems to be working on my end. Maybe I'm just confused as to what it
is you need here...
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-01-13 19:11:56 UTC
Permalink
@electrikjesus do you know
0001-DO-NOT-MERGE-temporary-workaround-for-Fds-whitelist-.patch
https://groups.google.com/d/msg/android-x86/BZZhufU_e6o/rnGszNjUDwAJ ?


圚 2017幎1月14日星期六 UTC+8䞊午3:08:25Jon West写道
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-13 20:34:00 UTC
Permalink
Oh? Why is the debug boot option still present in the Grub loader? Forget
to remove it? Anyway. Do you know what might be causing 7.1.1 to lock up
like this[see pictures]? This is happening on two different laptops. One is
an HP G60[C2D based] and the other is an Emachines EM250[Atom based]. Using
Rufus 2.8.886 to record the iso to a usb drive.

If it's something simple let me know and I'll fix it. Otherwise this is a
heads up. And just want to be clear, this is not a complaint, only a report
of problems discovered to assist development.
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-14 21:27:02 UTC
Permalink
I will look into support for those devices components. What build are you
trying with?
Post by The Captain
Oh? Why is the debug boot option still present in the Grub loader? Forget
to remove it? Anyway. Do you know what might be causing 7.1.1 to lock up
like this[see pictures]? This is happening on two different laptops. One is
an HP G60[C2D based] and the other is an Emachines EM250[Atom based]. Using
Rufus 2.8.886 to record the iso to a usb drive.
If it's something simple let me know and I'll fix it. Otherwise this is a
heads up. And just want to be clear, this is not a complaint, only a report
of problems discovered to assist development.
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-16 01:56:17 UTC
Permalink
Um, the aforementioned 7.1.1, specifically,
bliss-x86_32bit_n7.1.1_01.11.17_01_r12_02.iso and
bliss-x86_64bit_n7.1.1_01.11.17_r12_02_ej.iso. If there are newer versions
available, I'd be happy to try them. Got these two from the Bliss Google
Drive page.
Post by Jon West
I will look into support for those devices components. What build are you
trying with?
Post by The Captain
Oh? Why is the debug boot option still present in the Grub loader? Forget
to remove it? Anyway. Do you know what might be causing 7.1.1 to lock up
like this[see pictures]? This is happening on two different laptops. One is
an HP G60[C2D based] and the other is an Emachines EM250[Atom based]. Using
Rufus 2.8.886 to record the iso to a usb drive.
If it's something simple let me know and I'll fix it. Otherwise this is a
heads up. And just want to be clear, this is not a complaint, only a report
of problems discovered to assist development.
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alexander Harvey
2017-01-15 05:50:12 UTC
Permalink
Um, the aforementioned 7.1.1, specifically,
bliss-x86_32bit_n7.1.1_01.11.17_01_r12_02.iso and
bliss-x86_64bit_n7.1.1_01.11.17_r12_02_ej.iso. If there are newer
version available, I'd be happy to try them. Got these two from the
Bliss Google Drive page.
Post by Jon West
I will look into support for those devices components. What build are you
trying with?
Post by The Captain
Oh? Why is the debug boot option still present in the Grub loader? Forget
to remove it? Anyway. Do you know what might be causing 7.1.1 to lock up
like this[see pictures]? This is happening on two different laptops. One is
an HP G60[C2D based] and the other is an Emachines EM250[Atom based]. Using
Rufus 2.8.886 to record the iso to a usb drive.
If it's something simple let me know and I'll fix it. Otherwise this is a
heads up. And just want to be clear, this is not a complaint, only a report
of problems discovered to assist development.
Post by Jon West
Debug mode will not work properly in Bliss. Most end users will use the
included Terminal and su. What do you need Debug mode for anyways?
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-16 14:41:27 UTC
Permalink
That Google Drive page is likely a testing build folder. Please use the AFH links from the XDA post. Those are the build I have verified ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-16 19:13:35 UTC
Permalink
Ah there's a new version. Testing now...
[bliss-x86_n7.1.1r12_01.12.17_mesa.13.1.0_kernel_4.10.iso]
Post by Jon West
That Google Drive page is likely a testing build folder. Please use the
AFH links from the XDA post. Those are the build I have verified ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-17 00:55:46 UTC
Permalink
This newer version now installs and fully boots. I didn't have such a
problem with the screen rotation, but the wifi worked once on first boot
and now refuses to come on, even after a few reboots.
Jon I fixed the screen rotation and now the only problem left is the Wi-Fi
needing to be manually connected.
A great ROM!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-17 01:16:18 UTC
Permalink
I try to post the info about these on my XDA thread. That build is really Alpha quality IMO. WiFi cuts out on me as well, alot. My other builds are the more stable ones. They are using kernel-4.4 & mesa-13.02. Although they don't have heard as wide hardware support as the kernel-4.10 builds, they are starting to get better and better each build. I will be posting a couple more builds using kernel-4.10rc4 & mesa-13.03. So far, they seem to be pretty stable. Still having some WiFi issues though, not as bad. So. When I do post them, please make sure you read the release post(post 3) before just downloading from the AFH folder. It might save you time.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-01-17 01:16:19 UTC
Permalink
I try to post the info about these on my XDA thread. That build is really Alpha quality IMO. WiFi cuts out on me as well, alot. My other builds are the more stable ones. They are using kernel-4.4 & mesa-13.02. Although they don't have heard as wide hardware support as the kernel-4.10 builds, they are starting to get better and better each build. I will be posting a couple more builds using kernel-4.10rc4 & mesa-13.03. So far, they seem to be pretty stable. Still having some WiFi issues though, not as bad. So. When I do post them, please make sure you read the release post(post 3) before just downloading from the AFH folder. It might save you time.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-17 02:12:11 UTC
Permalink
That's totally understandable and I think we all understand the alpha
nature of these builds. Personally, just help out the dev process with
input. If you ever want log files, let me know which ones you need[and how
to get them] and I'll be happy to help out. The Pixel launcher is lacking
compared to the likes of Nova, Apex or ADW and I'm not a fan personally.
There is also a problem with the current built that is a glitch. It's
missing a file manager. In the app list "Files" is present but there is not
shortcut in the app drawer for it and thus no way to run it easily. Of
course "Files" might not be a file manager at all. Other than the wifi and
file manager issue this built seems solid! The Sony based theme manager is
very cool option. Though the CM Theme engine seems to have more support on
the Play Store[maybe?], the options with the Sony one seem more expansive.
The UI seems smooth and fluid. So far so go.

Bliss 6.4 is very cool, even accounting for the DPI glitch which, as stated
above, is easily solved. It too bad it's no longer supported..
Post by Jon West
I try to post the info about these on my XDA thread. That build is really
Alpha quality IMO. WiFi cuts out on me as well, alot. My other builds are
the more stable ones. They are using kernel-4.4 & mesa-13.02. Although they
don't have heard as wide hardware support as the kernel-4.10 builds, they
are starting to get better and better each build. I will be posting a
couple more builds using kernel-4.10rc4 & mesa-13.03. So far, they seem to
be pretty stable. Still having some WiFi issues though, not as bad. So.
When I do post them, please make sure you read the release post(post 3)
before just downloading from the AFH folder. It might save you time.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Musab Adam
2017-01-14 17:15:01 UTC
Permalink
Oh? Why is the debug boot option still present in the Grub loader? Forget to remove it? Anyway. Do you know what might be causing 7.1.1 to lock up like this[see pictures]? This is happening on two different laptops. One is an HP G60[C2D based] and the other is an Emachines EM250[Atom based]. Using Rufus 2.8.886 to record the iso to a usb drive.
If it's something simple let me know and I'll fix it. Otherwise this is a heads up. And just want to be clear, this is not a complaint, only a report of problems discovered to assist development.
On Friday, January 13, 2017 at 12:08:25 PM UTC-7, Jon West wrote:Debug mode will not work properly in Bliss. Most end users will use the included Terminal and su. What do you need Debug mode for anyways?
if you have access to gparted from Linux, do a check and repair on the partition you installed android on, that worked for me
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-16 08:20:19 UTC
Permalink
The partition is freshly created followed by a fresh install of the iso in
question using the built-in utility of the installer. The same problem
occurs even when using an external partition tool.
Post by The Captain
Oh? Why is the debug boot option still present in the Grub loader?
Forget to remove it? Anyway. Do you know what might be causing 7.1.1 to
lock up like this[see pictures]? This is happening on two different
laptops. One is an HP G60[C2D based] and the other is an Emachines
EM250[Atom based]. Using Rufus 2.8.886 to record the iso to a usb drive.
Post by The Captain
If it's something simple let me know and I'll fix it. Otherwise this is
a heads up. And just want to be clear, this is not a complaint, only a
report of problems discovered to assist development.
Post by The Captain
On Friday, January 13, 2017 at 12:08:25 PM UTC-7, Jon West wrote:Debug
mode will not work properly in Bliss. Most end users will use the included
Terminal and su. What do you need Debug mode for anyways?
if you have access to gparted from Linux, do a check and repair on the
partition you installed android on, that worked for me
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Russ B
2017-01-15 20:52:27 UTC
Permalink
Seems to work pretty well, though the display/graphics driver could be improved to better support Intel HD/Iris graphics.

One thing... It says the SU binary needs to be updated. How do I update the Super SU binary on Android-x86?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Larry Underhill
2017-01-15 22:48:46 UTC
Permalink
I installed bliss-x86_64_n7.1.1_01.11.17_r12_02_ej.iso on a Lenovo ThinkPad Twist 33476WU from USB. Very impressive! Smooth and quick. A few deficiencies are:
1. WiFi does not reconnect after sleep or boot; must be reconnected manually
2. Microphone is not functioning EDIT: IT DOES WORK
3. Screen rotation is not functioning natively; can be forced using an app
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alexander Harvey
2017-01-16 01:53:14 UTC
Permalink
How did you get it to run? It gets stuck on the login screen on every
machine I tested it on[see the above pics].
Post by Larry Underhill
1. WiFi does not reconnect after sleep or boot; must be reconnected manually
2. Microphone is not functioning EDIT: IT DOES WORK
3. Screen rotation is not functioning natively; can be forced using an app
--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alexander Harvey
2017-01-16 01:51:14 UTC
Permalink
Quote; "How do I update the Super SU binary on Android-x86?"

An easy solution, but not readily obvious. Make sure Root access is
enabled. Run SuperSU and when it prompts you, choose to update the su
binaries choosing the "normal" method. Then reboot and SuperSU will
become your default root access utility.
Post by Russ B
Seems to work pretty well, though the display/graphics driver could be improved to better support Intel HD/Iris graphics.
One thing... It says the SU binary needs to be updated. How do I update the Super SU binary on Android-x86?
--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Russ B
2017-01-16 08:04:15 UTC
Permalink
I tried that.  The update always fails..
Post by Alexander Harvey
Quote; "How do I update the Super SU binary on Android-x86?"
An easy solution, but not readily obvious. Make sure Root access is
enabled. Run SuperSU and when it prompts you, choose to update the su
binaries choosing the "normal" method. Then reboot and SuperSU will
become your default root access utility.
Post by Russ B
Seems to work pretty well, though the display/graphics driver could
be improved to better support Intel HD/Iris graphics.
Post by Russ B
One thing... It says the SU binary needs to be updated. How do I
update the Super SU binary on Android-x86?
Post by Russ B
--
You received this message because you are subscribed to a topic in
the Google Groups "Android-x86" group.
Post by Russ B
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
Post by Russ B
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-16 08:22:06 UTC
Permalink
With the CM version of root, it works on a per-boot basis. You have to go
into settings and enable root after every reboot. The same is required just
before updating SuperSu.
I tried that. The update always fails..
Post by Alexander Harvey
Quote; "How do I update the Super SU binary on Android-x86?"
An easy solution, but not readily obvious. Make sure Root access is
enabled. Run SuperSU and when it prompts you, choose to update the su
binaries choosing the "normal" method. Then reboot and SuperSU will
become your default root access utility.
Post by Russ B
Seems to work pretty well, though the display/graphics driver could be improved to better support Intel HD/Iris graphics.
One thing... It says the SU binary needs to be updated. How do I update the Super SU binary on Android-x86?
--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-01-27 08:49:08 UTC
Permalink
Ok, so testing with the latest version[
bliss-x86_n7.1.1r12_01.16.17_kernel-4.10_mesa-17.0.dev.iso ] has gone well
in all aspects except the wifi which is now not working at all. With the
previous version it was working on first boot[during the setup wizard] and
then not after. Everything else work smooth as silk. Fix the wifi and
you're gold!
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Wesley Henrique
2017-01-30 22:48:09 UTC
Permalink
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
Has as you create Bliss Rom based on Android-x86 6.0 r2 ?.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alexander Harvey
2017-01-30 22:51:33 UTC
Permalink
Sort of. It's called Bliss 6.4 and is based on Android 6, but they
have moved development to 7.1.1 so there will not be any further
updates to 6.4
Post by Wesley Henrique
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of rolling
out 7.1.1r12, and I should have a build or two hitting the downloads site
soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
Has as you create Bliss Rom based on Android-x86 6.0 r2 ?.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Wesley Henrique
2017-02-02 02:19:57 UTC
Permalink
More when they go post that new version?.

Em segunda-feira, 30 de janeiro de 2017 20:51:39 UTC-2, The Captain
Post by Alexander Harvey
Sort of. It's called Bliss 6.4 and is based on Android 6, but they
have moved development to 7.1.1 so there will not be any further
updates to 6.4
Em quarta-feira, 11 de janeiro de 2017 14:39:08 UTC-2, Jon West
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss
AOSP
Post by Jon West
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling
Post by Jon West
out 7.1.1r12, and I should have a build or two hitting the downloads
site
Post by Jon West
soon.
The second post on the XDA thread also contains a link to our update
MOD
Post by Jon West
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot
enabled
Post by Jon West
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel.
Our
Post by Jon West
changes to android-x86's kernel-4.4 branch are purely for
compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
Has as you create Bliss Rom based on Android-x86 6.0 r2 ?.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-02-02 15:18:30 UTC
Permalink
I post experimental builds of the new version weekly in the unstable branch and monthly in the stable branch
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Thomas B. Prost
2017-02-04 15:06:50 UTC
Permalink
Post by Jon West
I post experimental builds of the new version weekly in the unstable branch and monthly in the stable branch
Could you please post a link here ?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Harkaman Shivakoti
2017-02-04 16:16:21 UTC
Permalink
@Thomas Prost
https://www.androidfilehost.com/?w=files&flid=136638
Post by Jon West
Post by Jon West
I post experimental builds of the new version weekly in the unstable
branch and monthly in the stable branch
Could you please post a link here ?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Francesco Montefoschi
2017-02-03 12:56:01 UTC
Permalink
Hi Jon. I have built the ROM. Great work!
Two notes:
- gapps x86_64 repo is missing from repo; is that intended?
- I am unable to use adb wireless (connection is always unauthorized)

Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-02-05 13:09:15 UTC
Permalink
Gapps syncs for me just fine, but I usually also $repo sync -j20
--force-sync --force-broken after everything finishes the initial sync

On Saturday, February 4, 2017 at 5:33:08 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Hi Jon. I have built the ROM. Great work!
- gapps x86_64 repo is missing from repo; is that intended?
- I am unable to use adb wireless (connection is always unauthorized)
Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Francesco Montefoschi
2017-02-05 18:12:22 UTC
Permalink
It syncs fine, but it looks like the x86_64 repo is missing:

Compare https://github.com/BlissRoms-x86/manifest/blob/n7.1.1-x86/default.xml#L125
to https://github.com/opengapps/aosp_build/blob/master/README.md#getting-started
Post by Jon West
Gapps syncs for me just fine, but I usually also $repo sync -j20
--force-sync --force-broken after everything finishes the initial sync
On Saturday, February 4, 2017 at 5:33:08 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Hi Jon. I have built the ROM. Great work!
- gapps x86_64 repo is missing from repo; is that intended?
- I am unable to use adb wireless (connection is always unauthorized)
Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-02-06 14:14:49 UTC
Permalink
I see what you're saying. I've never used the x86_64 branch, because the
x86 branch seems to be working fine on 64bit. I will try and add it to a
few test builds and see if there are any improvements though.

On Sunday, February 5, 2017 at 1:12:23 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Compare
https://github.com/BlissRoms-x86/manifest/blob/n7.1.1-x86/default.xml#L125
to
https://github.com/opengapps/aosp_build/blob/master/README.md#getting-started
Post by Jon West
Gapps syncs for me just fine, but I usually also $repo sync -j20
--force-sync --force-broken after everything finishes the initial sync
On Saturday, February 4, 2017 at 5:33:08 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Hi Jon. I have built the ROM. Great work!
- gapps x86_64 repo is missing from repo; is that intended?
- I am unable to use adb wireless (connection is always unauthorized)
Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Francesco Montefoschi
2017-02-06 14:43:38 UTC
Permalink
I think improvements would be visible only on JNI code included in some
gapps. Anyway, adding the x86_64 won't hurt (except there is another remote
to fetch).
Did you get adb wireless working? I am still stuck on "unauthorized device".
Post by Jon West
I see what you're saying. I've never used the x86_64 branch, because the
x86 branch seems to be working fine on 64bit. I will try and add it to a
few test builds and see if there are any improvements though.
On Sunday, February 5, 2017 at 1:12:23 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Compare
https://github.com/BlissRoms-x86/manifest/blob/n7.1.1-x86/default.xml#L125
to
https://github.com/opengapps/aosp_build/blob/master/README.md#getting-started
Post by Jon West
Gapps syncs for me just fine, but I usually also $repo sync -j20
--force-sync --force-broken after everything finishes the initial sync
On Saturday, February 4, 2017 at 5:33:08 PM UTC-5, Francesco Montefoschi
Post by Francesco Montefoschi
Hi Jon. I have built the ROM. Great work!
- gapps x86_64 repo is missing from repo; is that intended?
- I am unable to use adb wireless (connection is always unauthorized)
Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Wesley Henrique
2017-02-05 05:09:55 UTC
Permalink
I tested it worked perfectly with this version of Bliss ROM. :D

*bliss-x86_n7.1.1_01.11.17_01_r12_02.iso*
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Wesley Henrique
2017-02-05 21:36:52 UTC
Permalink
Help-me, infinity loop on *bliss-x86_n7.1.1_01.11.17_01_r12_02.iso. :(*
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Wesley Massumbukolt
2017-02-06 21:24:27 UTC
Permalink
Hello

Great job on that project you're making!

Do you know if you have tested these builds on a Surface Pro 4 to get the
touchscreen driver working?
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-02-07 12:19:45 UTC
Permalink
No touchscreen yet, but working on it. Read the main thread to see info specific to that device.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Henri Koivuneva
2017-02-26 13:57:32 UTC
Permalink
Quick note: The masquerade github path has changed from
"TeamSubstratum/masquerade" to "substratum/masquerade". I noticed that when
syncing just a while ago!

Thank you for this awesome stuff.. I LOVE Bliss on my Surface Pro 3! It
indeed is Blissful :D I use it mainly to read comics, books and stuff on
the web and randomly to watch YouTube and play a bit of Monument Valley.
The reading experience is countless of times better than on Windows.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
adam dubuque
2017-02-26 23:47:10 UTC
Permalink
I know this is peobably a dumb question but will this work on Baytrail devices specifically the sound, bluetooth, wifi, screen rotation, etc.
it would have to have had the realtek driver for linux installed????
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-10 18:22:31 UTC
Permalink
Using the latest stable release,
bliss-x86_n7.1.1r22_03.03.17_k4.4-blissified_01.iso , The install does well
but on first boot the system hangs on the Bliss logo screen and stays
there. The system isn't locked as the Bliss logo continues it's animation
cycle. Crtl+Alt+Del still works and reboots the system but then returns to
the Bliss logo. Again, this is being tested on an Atom N270 based netbook
and a C2D T8300 based laptop. As this has happened with the past two builds
in a row, could it be safe to conclude that the Bliss team is no longer
supporting older platforms? This would be a shame as said systems can run
Android 7.1.1 well.
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-03-11 13:15:38 UTC
Permalink
Just curious, how long did you let it boot? My Acer takes up to 15 minutes on first boot sometimes
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-11 18:48:43 UTC
Permalink
Solid 20 minutes at least. Still, that's quite a long time for a first run.
I'll try it again today. Perhaps it was a one off.
Post by Jon West
Just curious, how long did you let it boot? My Acer takes up to 15 minutes
on first boot sometimes
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-11 22:53:26 UTC
Permalink
Well tried again a few times. Tried redownloading just in case. The first
attempt was a reformat with ext4. And it hung on the Bliss logo again. Then
I tried ext3 and ext2. In both of those cases it hung in the "Detecting
Android-x86... found at /devsda1" screen. So ya. It's doing this on both
systems. I even tried it on an i7 based system with the same results. So
I'm at a loss.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-03-12 18:00:42 UTC
Permalink
I'll check the installer once again. There is a possibility something got messed with in my latest shuffle between build computers.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-13 23:52:32 UTC
Permalink
Ok cool. If you do find something went amiss, let us know and I'll happily
give it another go.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-03-15 14:26:09 UTC
Permalink
I did find the culprit. Should have an update soon once I get everything
tested first
Post by The Captain
Ok cool. If you do find something went amiss, let us know and I'll happily
give it another go.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-23 10:39:57 UTC
Permalink
Saw that you updated the 64bit ISO, is there an update for the 32bit
version?
Post by Jon West
I did find the culprit. Should have an update soon once I get everything
tested first
Post by The Captain
Ok cool. If you do find something went amiss, let us know and I'll
happily give it another go.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-23 10:43:36 UTC
Permalink
Also, What is the point of the EDU "Rootless" branch? I wouldn't even touch
Android without root and it seems certain that most others interested in
this wouldn't either.
Post by The Captain
Saw that you updated the 64bit ISO, is there an update for the 32bit
version?
Post by Jon West
I did find the culprit. Should have an update soon once I get everything
tested first
Post by The Captain
Ok cool. If you do find something went amiss, let us know and I'll
happily give it another go.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Henri Koivuneva
2017-03-23 14:51:10 UTC
Permalink
EDUcation. In there it's highly beneficial to NOT have root in many, many
use cases.

Even I have built versions without root for regular use, that way I can be
sure the user doesn't mess up anything too bad and that their data isn't as
easy to compromise as it'd be with root.

They can still install substratum themes and do all kinds of fun stuff. If
they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!

Bliss is awesome. The name fits perfectly!

23.3.2017 12.43 "The Captain" <***@gmail.com> kirjoitti:

Also, What is the point of the EDU "Rootless" branch? I wouldn't even touch
Android without root and it seems certain that most others interested in
this wouldn't either.
Post by The Captain
Saw that you updated the 64bit ISO, is there an update for the 32bit
version?
Post by Jon West
I did find the culprit. Should have an update soon once I get everything
tested first
Post by The Captain
Ok cool. If you do find something went amiss, let us know and I'll
happily give it another go.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-23 16:51:44 UTC
Permalink
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many, many
use cases.
Even I have built versions without root for regular use, that way I can be
sure the user doesn't mess up anything too bad and that their data isn't as
easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff. If
they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
Also, What is the point of the EDU "Rootless" branch? I wouldn't even
touch Android without root and it seems certain that most others interested
in this wouldn't either.
Post by The Captain
Saw that you updated the 64bit ISO, is there an update for the 32bit
version?
Post by Jon West
I did find the culprit. Should have an update soon once I get everything
tested first
Post by The Captain
Ok cool. If you do find something went amiss, let us know and I'll
happily give it another go.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-23 16:52:35 UTC
Permalink
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many, many
use cases.
Even I have built versions without root for regular use, that way I can be
sure the user doesn't mess up anything too bad and that their data isn't as
easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff. If
they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-03-23 21:29:17 UTC
Permalink
do you know safety net ? do you know pokemon go ? do you know love live ?

圚 2017幎3月24日星期五 UTC+8䞊午12:52:35The Captain写道
Post by The Captain
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many, many
use cases.
Even I have built versions without root for regular use, that way I can
be sure the user doesn't mess up anything too bad and that their data isn't
as easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff.
If they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
lexluthermiester
2017-03-24 09:05:08 UTC
Permalink
What does any of that have to do with this discussion?
Post by youling 257
do you know safety net ? do you know pokemon go ? do you know love live ?
圚 2017幎3月24日星期五 UTC+8䞊午12:52:35The Captain写道
Post by The Captain
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many,
many use cases.
Even I have built versions without root for regular use, that way I can
be sure the user doesn't mess up anything too bad and that their data isn't
as easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff.
If they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Henri Koivuneva
2017-03-24 10:14:56 UTC
Permalink
I think youling257 meant if he knows that Pokemon go and that other game
won't run and SafetyNet checks won't pass with regular root.

I can run safetynet checking apps and games like Pokemon go with systemless
magisk, magisksu and magisk hide though, as of now, on my phone.

24.3.2017 11.05 "lexluthermiester" <***@gmail.com> kirjoitti:

What does any of that have to do with this discussion?
Post by youling 257
do you know safety net ? do you know pokemon go ? do you know love live ?
圚 2017幎3月24日星期五 UTC+8䞊午12:52:35The Captain写道
Post by The Captain
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many,
many use cases.
Even I have built versions without root for regular use, that way I can
be sure the user doesn't mess up anything too bad and that their data isn't
as easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff.
If they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-24 10:40:51 UTC
Permalink
I didn't understand Youling257's post either. IMO, SafetyNet is not all
that useful and any app that refuses to run because the system is rooted is
not worthy of use. But yes, using utilities that hide root are easy to
install and use.
Post by Henri Koivuneva
I think youling257 meant if he knows that Pokemon go and that other game
won't run and SafetyNet checks won't pass with regular root.
I can run safetynet checking apps and games like Pokemon go with
systemless magisk, magisksu and magisk hide though, as of now, on my phone.
What does any of that have to do with this discussion?
Post by youling 257
do you know safety net ? do you know pokemon go ? do you know love live ?
圚 2017幎3月24日星期五 UTC+8䞊午12:52:35The Captain写道
Post by The Captain
Ah, I see. And such makes sense for certain environments. Of course that
does limit a great many very useful utilities, such as a firewall,
security, backup and customizations apps.
Post by Henri Koivuneva
EDUcation. In there it's highly beneficial to NOT have root in many,
many use cases.
Even I have built versions without root for regular use, that way I can
be sure the user doesn't mess up anything too bad and that their data isn't
as easy to compromise as it'd be with root.
They can still install substratum themes and do all kinds of fun stuff.
If they really need root, they can ask for the necessary images and replace
the rootless ones. Easy!
Bliss is awesome. The name fits perfectly!
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-03-24 11:48:48 UTC
Permalink
What he's trying to say is that a rootless build allows him, and many others like him to play Pokemon Go, ?Love Live? and a few other games that having a rooted build allows.
I use Bliss-x86 to get stuff done, but many other use it to play games, while others use it as a media center, and the list could go on. I have no doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-03-24 11:53:56 UTC
Permalink
*having a rooted build doesn't allow
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-25 00:58:51 UTC
Permalink
That was understandable. The thing is, there are utilities that can hide
root from apps. They're easy to use so his argument isn't all that logical.
It just shows that he wasn't aware of them. Thing is, if you're going to
make versions without root, at least give people and option to root if they
want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play games,
while others use it as a media center, and the list could go on. I have no
doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-03-25 01:34:46 UTC
Permalink
rootless build for the Ordinary user .

https://groups.google.com/d/msg/android-x86/311n2ivCLYw/hfIZnqkXBwAJ
https://groups.google.com/d/msg/android-x86/311n2ivCLYw/pXPubB4aBwAJ

圚 2017幎3月25日星期六 UTC+8䞊午8:58:51The Captain写道
Post by The Captain
That was understandable. The thing is, there are utilities that can hide
root from apps. They're easy to use so his argument isn't all that logical.
It just shows that he wasn't aware of them. Thing is, if you're going to
make versions without root, at least give people and option to root if they
want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play games,
while others use it as a media center, and the list could go on. I have no
doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
The Captain
2017-03-25 02:34:37 UTC
Permalink
I see what you're saying. The point I was trying to make is that it needs
to be the choice of the user. With a standard AndroidX86 iso, the question
of whether to make the system writable[and thus have root] is asked during
installation. This is useful as it leave the choice to the person
installing. PhoenixOS have taken that a step further by placing the root
option in the "Developer Options" section of the settings menu which
changes back to default upon reboot. The EDU versions are good. Just hoping
that this "rootless" thing doesn't spread to the regular distro's.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-03-25 03:05:24 UTC
Permalink
you say developer option root access disable、app only、app and adb ? that
for superuserPhoenix OS and cwhuang Android x86 use superuser .
lineage use superuseri replace with supersu systemlesseven though
“developer option root access disable ” still can root by supersu .
Bliss x86 root build use supersu .

圚 2017幎3月25日星期六 UTC+8䞊午10:34:38The Captain写道
Post by The Captain
I see what you're saying. The point I was trying to make is that it needs
to be the choice of the user. With a standard AndroidX86 iso, the question
of whether to make the system writable[and thus have root] is asked during
installation. This is useful as it leave the choice to the person
installing. PhoenixOS have taken that a step further by placing the root
option in the "Developer Options" section of the settings menu which
changes back to default upon reboot. The EDU versions are good. Just hoping
that this "rootless" thing doesn't spread to the regular distro's.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Henri Koivuneva
2017-03-25 07:58:21 UTC
Permalink
Well as far as I understand it, the point of the EDU branch & builds IS to
be rootless... Others do have root so you can use those :D
Post by The Captain
I see what you're saying. The point I was trying to make is that it needs
to be the choice of the user. With a standard AndroidX86 iso, the question
of whether to make the system writable[and thus have root] is asked during
installation. This is useful as it leave the choice to the person
installing. PhoenixOS have taken that a step further by placing the root
option in the "Developer Options" section of the settings menu which
changes back to default upon reboot. The EDU versions are good. Just hoping
that this "rootless" thing doesn't spread to the regular distro's.
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/android-x86/omGg6QZlEGc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-03-25 01:44:28 UTC
Permalink
Alt+f1mv /su/xbin_bind/su /su/xbin_bind/1su mv /su/xbin_bind/1su
/su/xbin_bind/su switch root and rootless

圚 2017幎3月25日星期六 UTC+8䞊午8:58:51The Captain写道
Post by The Captain
That was understandable. The thing is, there are utilities that can hide
root from apps. They're easy to use so his argument isn't all that logical.
It just shows that he wasn't aware of them. Thing is, if you're going to
make versions without root, at least give people and option to root if they
want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play games,
while others use it as a media center, and the list could go on. I have no
doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-05-17 15:44:57 UTC
Permalink
Hey Youling, Would you please try and explain to us how you were able to
get systemless magisk running on your builds? You seem to be the only one
able to do so, and we would love a little help in figuring it out.
Post by youling 257
Alt+f1mv /su/xbin_bind/su /su/xbin_bind/1su mv /su/xbin_bind/1su
/su/xbin_bind/su switch root and rootless
圚 2017幎3月25日星期六 UTC+8䞊午8:58:51The Captain写道
Post by The Captain
That was understandable. The thing is, there are utilities that can hide
root from apps. They're easy to use so his argument isn't all that logical.
It just shows that he wasn't aware of them. Thing is, if you're going to
make versions without root, at least give people and option to root if they
want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play games,
while others use it as a media center, and the list could go on. I have no
doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-05-17 21:27:49 UTC
Permalink
I won't explain my initrd.img'initi edit it last month.
i will explain ramdisk sbin/magic_mask.sh .
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-05-17 21:37:09 UTC
Permalink
# Stage 1
log_print "* Stage 1: Mount system and vendor mirrors"
SYSTEMBLOCK=`mount | grep " /system " | awk '{print $1}' | awk '{print substr($0,6)}'`
mkdir -p $MIRRDIR/system
busybox mount -o noatime /dev/block/$SYSTEMBLOCK $MIRRDIR/system

/dev/block/$SYSTEMBLOCK can be loop0(system.img) and loop1(system.sfs loop0、system.img loop1).

if /dev/sda5 mount on /mnt, /mnt/$SRC/data mount on /android/data, /dev/sda6 mount on /android/system, /dev/block/$SYSTEMBLOCK can be sda6, sda6 is whole android system .
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-05-23 07:57:42 UTC
Permalink
圚 2017幎5月17日星期䞉 UTC+8䞋午11:44:57Jon West写道
Post by Jon West
Hey Youling, Would you please try and explain to us how you were able to
get systemless magisk running on your builds? You seem to be the only one
able to do so, and we would love a little help in figuring it out.
Post by youling 257
Alt+f1mv /su/xbin_bind/su /su/xbin_bind/1su mv /su/xbin_bind/1su
/su/xbin_bind/su switch root and rootless
圚 2017幎3月25日星期六 UTC+8䞊午8:58:51The Captain写道
Post by The Captain
That was understandable. The thing is, there are utilities that can hide
root from apps. They're easy to use so his argument isn't all that logical.
It just shows that he wasn't aware of them. Thing is, if you're going to
make versions without root, at least give people and option to root if they
want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play games,
while others use it as a media center, and the list could go on. I have no
doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-05-23 08:07:28 UTC
Permalink
if [ -n "$mnt" ]; then
BLOCK=`blkid | grep -m1 $mnt | cut -d : -f 1`
try_mount rw $BLOCK /mnt
else
try_mount rw $dev /mnt || return 1
fi

$mnt can be /dev/xxx and UUID 
mnt=e09579e5-87f6-416b-991c-4ac562bdddcemnt=mmcblk1p9

if mount /mnt/$SRC/system folder on /android/systemmy idea

elif [ -d /mnt/$SRC/system ]; then

remount_rw

mount --bind /mnt/$SRC/system system

mount -o loop,noatime /mnt/$SRC/magisk.img magisk

mount --bind /mnt/$SRC/system magisk/.core/system


# Stage 1

log_print "* Stage 1: Mount system and vendor mirrors"

SYSTEMBLOCK=`mount | grep " /system " | awk '{print $1}' | awk '{print substr($0,6)}'`

mkdir -p $MIRRDIR/system

if [ -e $COREDIR/system/build.prop ]; then

mount -o bind,noatime $COREDIR/system $MIRRDIR/system

else

busybox mount -o noatime /dev/block/$SYSTEMBLOCK $MIRRDIR/system

fi


圚 2017幎5月23日星期二 UTC+8䞋午3:57:42youling 257写道
Post by youling 257
圚 2017幎5月17日星期䞉 UTC+8䞋午11:44:57Jon West写道
Post by Jon West
Hey Youling, Would you please try and explain to us how you were able to
get systemless magisk running on your builds? You seem to be the only one
able to do so, and we would love a little help in figuring it out.
Post by youling 257
Alt+f1mv /su/xbin_bind/su /su/xbin_bind/1su mv /su/xbin_bind/1su
/su/xbin_bind/su switch root and rootless
圚 2017幎3月25日星期六 UTC+8䞊午8:58:51The Captain写道
Post by The Captain
That was understandable. The thing is, there are utilities that can
hide root from apps. They're easy to use so his argument isn't all that
logical. It just shows that he wasn't aware of them. Thing is, if you're
going to make versions without root, at least give people and option to
root if they want/need it.
Post by Jon West
What he's trying to say is that a rootless build allows him, and many
others like him to play Pokemon Go, ?Love Live? and a few other games that
having a rooted build doesn't allow.
I use Bliss-x86 to get stuff done, but many other use it to play
games, while others use it as a media center, and the list could go on. I
have no doubt were all on the right track ;)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-04-03 17:04:00 UTC
Permalink
We have taken the time to release an x86 version of our popular ROM for Android. The goals of this project will be to stay in line with Bliss AOSP development, so that meand we shouldn't be any more than a week behind changes on their end. With that being said, we are in the process of rolling out 7.1.1r12, and I should have a build or two hitting the downloads site soon. 
The second post on the XDA thread also contains a link to our update MOD for the Android-x86 UEFI installer. This is a nondestructive method of installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled computer. Source links are also posted. 
These builds will also contain all the Surface patches in the kernel. Our changes to android-x86's kernel-4.4 branch are purely for compatibility. 
Enough banter, here's the link: https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
  
I posted a few new updates today for both the stable branch and the bleeding edge branch. Check the latest post on the XDA thread for more details :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-04-06 23:10:21 UTC
Permalink
Bliss-x86'ers!! If you're on one of the latest builds of Bliss-x86, you can
set Taskbar as you're navbar TODAY!!! Follow the link for a short
walkthrough :)
https://forum.xda-developers.com/showpost.php?p=71757350&postcount=290
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-04-07 02:42:44 UTC
Permalink
i don't think the navbar no use i use navbar tuner and now on tap .
the taskbar 3.3 version add back、home、recent buttonif you think can
instead of navbar .
the freeform windows is bad than remix os、Phoenix os、openthos .

圚 2017幎4月7日星期五 UTC+8䞊午7:10:22Jon West写道
Post by Jon West
Bliss-x86'ers!! If you're on one of the latest builds of Bliss-x86, you
can set Taskbar as you're navbar TODAY!!! Follow the link for a short
walkthrough :)
https://forum.xda-developers.com/showpost.php?p=71757350&postcount=290
Post by Jon West
We have taken the time to release an x86 version of our popular ROM for
Android. The goals of this project will be to stay in line with Bliss AOSP
development, so that meand we shouldn't be any more than a week behind
changes on their end. With that being said, we are in the process of
rolling out 7.1.1r12, and I should have a build or two hitting the
downloads site soon.
The second post on the XDA thread also contains a link to our update MOD
for the Android-x86 UEFI installer. This is a nondestructive method of
installing Bliss-x86, Android-x86 & RemixOS to a windows UEFI boot enabled
computer. Source links are also posted.
These builds will also contain all the Surface patches in the kernel. Our
changes to android-x86's kernel-4.4 branch are purely for compatibility.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-04-07 12:23:35 UTC
Permalink
If you are used to a different setup, then I do not recommend switching to Taskbar for your navigation just yet. I however, don't need anything fancy, so it works flawlessly for me. Bliss will still come stock I think, allowing users to choose for themselves what route they'd like.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
D.D.
2017-04-07 08:51:34 UTC
Permalink
Maybe someone in this thread may help me with my issue.

I need to activate HCE in my custom Bliss-x86 build. But I still did not
succeed with that. Please, look at the last few messages in this thread
<https://groups.google.com/forum/#!topic/android-x86/m1OusTUM6Nw>.

Thanks in advance.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-04-07 12:27:03 UTC
Permalink
We are only able to get working what we come across in our day to day adventures with Android-x86. I have yet to see a PC with NFC, nor can I think of a non-devious reason for a PC to use it other than a POS system. Maybe if they were more widely supported, we'd have a larger support base for NFC here.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
D.D.
2017-04-07 15:41:41 UTC
Permalink
Jon West

Well, I'd like to make external NFC readers work in Android-x86 on virtual
machine (VB). It makes sense when smartphone doesn't have a buil-in NFC or
it doesn't support specific standards. So, I had some plans of using those
readers as native NFC in Android OS. Among other things I want to test HCE
functionality of such NFC, e.g. to issue a virtual bank card etc. I could
say that NFC cards/tags are widely spreaded in many cities of our country.
They mainly used in the transport system as a payment method. To work with
such cards one needs a NFC adapter (reader). For this purpose I have
ACR1281U-C1 by ACS.

I think, the answer to my problem is the answer to this simple question -
what would you do if you wanted to activate some deactivated system app
(service)? Which things deserve your attention?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2017-04-07 20:25:00 UTC
Permalink
I would go through the manifest and make sure all the needed packages are
being called in either vendor/bliss/configs/common.mk or
device/generic/common/packages.mk.

In doing this, I am seeing that the NFC app isn't listed in either of those
places, so I would add "NfcNci \" to the packages.mk and see if that builds
OK. I might have removed it initially due to errors and completly forgot
about it. I'm ADD AF sometimes :)
Post by youling 257
Jon West
Well, I'd like to make external NFC readers work in Android-x86 on virtual
machine (VB). It makes sense when smartphone doesn't have a buil-in NFC or
it doesn't support specific standards. So, I had some plans of using those
readers as native NFC in Android OS. Among other things I want to test HCE
functionality of such NFC, e.g. to issue a virtual bank card etc. I could
say that NFC cards/tags are widely spreaded in many cities of our country.
They mainly used in the transport system as a payment method. To work with
such cards one needs a NFC adapter (reader). For this purpose I have
ACR1281U-C1 by ACS.
I think, the answer to my problem is the answer to this simple question -
what would you do if you wanted to activate some deactivated system app
(service)? Which things deserve your attention?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
D.D.
2017-04-08 14:40:34 UTC
Permalink
Jon West

Oh, you are right, it should be "*NfcNci*", not 'Nfc". So, after defining
that (there may be some additional NFC packages as "libnfc-nci",
"libnfc-nxp", "libnfc_nci_jni", "Tag", "com.android.nfc_extras") I finally
got the files compiled and the service built into the image. But for some
reason my image was broken - it was hangin' on partition selection screen.
Even with one "NfcNci" only (no other stuff).

But the image you sent me installed just fine! I see that NFC service is
really running. But to my great regret the whole OS is buggy as hell :( It
crashes on almost every thing I do, say installing .apk, adjusting
settings, opening some apps... I don't know what led to that. It might be
the absence of physical NFC hardware or something else. So, I could not
check HCE functionality due to regular crashes of the system. After each
such crash I get kernel panic on the next boot and have to reinstall the
system (or load from a snapshot as I work on VB). I have no clue how this
could be fixed (if it could).

Anyway thank you very much for your efforts! You helped a lot. :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2017-04-07 02:51:05 UTC
Permalink
http://forum.mobilism.org/viewtopic.php?f=438&t=2015706&hilit=taskbar

Taskbar (Donate Version) v3.3
New in 3.3:
&bull; Back, Home, and Recents buttons can be added to the Taskbar (under
"Advanced features")
&bull; New option to expand the recent apps area with whitespace, to make
the Taskbar full-width (under "Recent apps")
&bull; When upgrading to the Donate Version, Taskbar will show previews of
previously placed widgets that were used in the free version
&bull; Other fixes and improvements

Taskbar (Donate Version) v3.2 b137
&bull; Added option to only show currently running apps (requires Taskbar
to be installed in the system partition)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Greg McGee
2017-04-16 06:15:22 UTC
Permalink
The current 7.1.1-edu version works well on a Microcenter TW-100 booted
from USB (Has a std size USB3 port)
(atom dual core, 2GB RAM, 32GB flash disk, Goodix TS)
Wifi working, screen and TS in sync but 90 degrees out, the included
rotation lock in the top bar allows an easy work around.

Contains the annoying 8723bs wifi/BT chip, wifi works well, BT/FM not at
all of course, but minor issue.

Only ran it from usb, but it was fast and stable.

Actual file was
bliss-x86_64-EDU_n7.1.1r22_03.18.17_k4.4-blissified_rootless_02.iso

...Now if I could just get it running on my Lenovo X200 I'd have a daily,
the i965 drivers have been borked on Android-x86 on everything after KitKat.
(gfx driver craters)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
TheCaptain
2017-07-25 22:51:13 UTC
Permalink
Just wanted to chime in and let you all know that the latest version of
Bliss[OFFICIAL-20170614-2149_k4.9-ax86_m17.1.2_01] is working like a dream,
both the 32bit and 64bit. Not glitches, no problems. Loving it! It has
become my new daily driver on two of my systems.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...