Discussion:
Android-x86 7.1-rc1 released
(too old to reply)
Michael Goffioul
2017-06-08 11:06:53 UTC
Permalink
Did you solve the problem how low color depth when playing videos? It
didn't seem to be the case 2 days ago.

Michael.
I sent the email too quickly.
I'd like to say thanks to all
who helped to make it happen.
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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
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.
Martin
2017-06-09 10:07:50 UTC
Permalink
Thanks for great work on it again!

Suspend it's not working on my device, so...
In my opinion it's time to add another option in settings to disable
suspend.state and earlysuspend aswell.
I rather prefer have screen off than not working suspend. Sometimes I have
to reboot device to access androidx86 again, so it's unacceptable.
--
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-06-09 10:17:34 UTC
Permalink
sleep.earlysuspend=0 sleep.state=disabled

圚 2017幎6月9日星期五 UTC+8䞋午6:07:51Martin写道
Post by Martin
Thanks for great work on it again!
Suspend it's not working on my device, so...
In my opinion it's time to add another option in settings to disable
suspend.state and earlysuspend aswell.
I rather prefer have screen off than not working suspend. Sometimes I have
to reboot device to access androidx86 again, so it's unacceptable.
--
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.
Martin
2017-06-09 10:48:53 UTC
Permalink
Post by youling 257
sleep.earlysuspend=0 sleep.state=disabled
I know that, but it would be easier to enable/disable it from settings. Eg.
for new users, which don't know how do that.
--
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.
Martin Claudio Cota
2017-06-09 17:41:43 UTC
Permalink
Thanks for the great work, I was looking forward for Android N ! I used to
have Android M installed and just replaced the boot files on my HDD but on
this version I get a boot loop, is there any documentation on changes that
could apply to the GRUB settings between M and N version that could be
generating this kind of issue ?

I'm running this on a Gigabyte Brix J1900.

Thanks anyway, great job.
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-09 18:42:47 UTC
Permalink
Support successful on Nvidia Geforce 8400GS. Thanks. :D
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Krister Hallergard
2017-06-10 06:59:04 UTC
Permalink
Had a successful upgrade from 6.0-r3, details here https://goo.gl/21QMP0
--
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.
Krister Hallergard
2017-06-14 12:55:01 UTC
Permalink
Thanks, I was not aware of this with the new launcher! Also KODI solved
with the native bridge support, blog updated.
Post by Krister Hallergard
Had a successful upgrade from 6.0-r3, details here https://goo.gl/21QMP0
About the App Drawer, just press "^" icon.
Or swipe the below app line from bottom to top.
--
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.
Martin Claudio Cota
2017-06-10 14:39:15 UTC
Permalink
After making some modifications to my old Grub menu I was able to make it
boot. I used the GRUB created by the installer and modified to my HDD based
install using ext4. Unfortunatelly after rebooting, I get stuck on Android
screen. I added DATA=/android/data to the boot parameters, and all data is
there, but not sure why I get stuck on booting screen now.
--
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-06-10 15:36:06 UTC
Permalink
DATA=/android/data is wrongold methodit was wrongno anyting use.
new methodif DATA=/android/datacan't mkdir /mnt/$SRC/android/datacan't
mount on /android/data .
cwhuang need to explain $DATA usage .

else
remount_rw
mkdir -p /mnt/$SRC/$DATA
mount --bind /mnt/$SRC/$DATA data

圚 2017幎6月10日星期六 UTC+8䞋午10:39:15Martin Claudio Cota写道
Post by Martin Claudio Cota
After making some modifications to my old Grub menu I was able to make it
boot. I used the GRUB created by the installer and modified to my HDD based
install using ext4. Unfortunatelly after rebooting, I get stuck on Android
screen. I added DATA=/android/data to the boot parameters, and all data is
there, but not sure why I get stuck on booting screen now.
--
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-06-10 15:42:34 UTC
Permalink
you can use DATA=android/datawill mkdir -p /mnt/$SRC/android/datamount on
/android/data .

圚 2017幎6月10日星期六 UTC+8䞋午11:36:06youling 257写道
Post by youling 257
DATA=/android/data is wrongold methodit was wrongno anyting use.
new methodif DATA=/android/datacan't mkdir /mnt/$SRC/android/datacan't
mount on /android/data .
cwhuang need to explain $DATA usage .
else
remount_rw
mkdir -p /mnt/$SRC/$DATA
mount --bind /mnt/$SRC/$DATA data
圚 2017幎6月10日星期六 UTC+8䞋午10:39:15Martin Claudio Cota写道
Post by Martin Claudio Cota
After making some modifications to my old Grub menu I was able to make it
boot. I used the GRUB created by the installer and modified to my HDD based
install using ext4. Unfortunatelly after rebooting, I get stuck on Android
screen. I added DATA=/android/data to the boot parameters, and all data is
there, but not sure why I get stuck on booting screen now.
--
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-06-10 15:56:58 UTC
Permalink
seem can mkdir -p /mnt/$SRC/android/datamount no problemif
DATA=/android/data

圚 2017幎6月10日星期六 UTC+8䞋午11:36:06youling 257写道
Post by youling 257
DATA=/android/data is wrongold methodit was wrongno anyting use.
new methodif DATA=/android/datacan't mkdir /mnt/$SRC/android/datacan't
mount on /android/data .
cwhuang need to explain $DATA usage .
else
remount_rw
mkdir -p /mnt/$SRC/$DATA
mount --bind /mnt/$SRC/$DATA data
圚 2017幎6月10日星期六 UTC+8䞋午10:39:15Martin Claudio Cota写道
Post by Martin Claudio Cota
After making some modifications to my old Grub menu I was able to make it
boot. I used the GRUB created by the installer and modified to my HDD based
install using ext4. Unfortunatelly after rebooting, I get stuck on Android
screen. I added DATA=/android/data to the boot parameters, and all data is
there, but not sure why I get stuck on booting screen now.
--
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.
Martin Claudio Cota
2017-06-10 17:16:20 UTC
Permalink
Sorry, I don't understand what's wrong. I used to have a /android/data path
for storage, used to work on Android M, and the path was pointed out on my
kernel file in grub as DATA=/android/data. How is it supposed to work on
android N ?

Thanks.
Post by youling 257
seem can mkdir -p /mnt/$SRC/android/datamount no problemif
DATA=/android/data
圚 2017幎6月10日星期六 UTC+8䞋午11:36:06youling 257写道
Post by youling 257
DATA=/android/data is wrongold methodit was wrongno anyting use.
new methodif DATA=/android/datacan't mkdir /mnt/$SRC/android/datacan't
mount on /android/data .
cwhuang need to explain $DATA usage .
else
remount_rw
mkdir -p /mnt/$SRC/$DATA
mount --bind /mnt/$SRC/$DATA data
圚 2017幎6月10日星期六 UTC+8䞋午10:39:15Martin Claudio Cota写道
Post by Martin Claudio Cota
After making some modifications to my old Grub menu I was able to make
it boot. I used the GRUB created by the installer and modified to my HDD
based install using ext4. Unfortunatelly after rebooting, I get stuck on
Android screen. I added DATA=/android/data to the boot parameters, and all
data is there, but not sure why I get stuck on booting screen now.
--
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.
Martin Claudio Cota
2017-06-12 19:58:40 UTC
Permalink
Indeed, removing DATA from my grub setings fixed my booting problem. All my
info was there and it's working amazingly well now. Great version by the
way.... first time I try Nougat.

Thanks.
There is no change. You don't need to set DATA=.
But if you set before, you can keep it as.
androidboot.selinux=permissive
寫道
Sorry, I don't understand what's wrong. I used to have a /android/data
path for storage, used to work on Android M, and the path was pointed out
on my kernel file in grub as DATA=/android/data. How is it supposed to work
on android N ?
Thanks.
seem can mkdir -p /mnt/$SRC/android/datamount no problemif
DATA=/android/data
圚 2017幎6月10日星期六 UTC+8䞋午11:36:06youling 257写道
Post by youling 257
DATA=/android/data is wrongold methodit was wrongno anyting use.
new methodif DATA=/android/datacan't mkdir
/mnt/$SRC/android/datacan't mount on /android/data .
cwhuang need to explain $DATA usage .
else
remount_rw
mkdir -p /mnt/$SRC/$DATA
mount --bind /mnt/$SRC/$DATA data
圚 2017幎6月10日星期六 UTC+8䞋午10:39:15Martin Claudio Cota写道
Post by Martin Claudio Cota
After making some modifications to my old Grub menu I was able to make
it boot. I used the GRUB created by the installer and modified to my HDD
based install using ext4. Unfortunatelly after rebooting, I get stuck on
Android screen. I added DATA=/android/data to the boot parameters, and all
data is there, but not sure why I get stuck on booting screen now.
--
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
<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.
Raymond Lai
2017-06-11 13:56:01 UTC
Permalink
Glad to see it works so good on my GPD WIN.

A quick 5 minutes test

- screen brightness working
- sound comes out of speaker
- Youtube is working

So magic that it's still using kernel 4.9!
(Seriously, I won't mind older kernels)

May try using HDMI out, earphone, joypad, bluetooth, 3D games, etc... once
I got time to set it up on my machine.

Kudos to the team - thanks again for the hard work!
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
YoungJoon Lee
2017-06-11 23:10:49 UTC
Permalink
Hello, thanks for great work.

I download it and boot using usb stick. But I can't found my NVMe SSD on installer. So, I get source using repo command and build kernel and source.

Now I can see my SSD but I can't select it. When I push enter key on my SSD, screen is prompt and return to device select menu without any error message. I boot into debug mode and found that /dev/nvmen1pn is present. How can I solve this problem? Thank you very much for reading.
--
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.
Kristy Anon
2017-06-09 12:19:33 UTC
Permalink
Hi Chih-Wei,
Thanks a lot for this build!
I'm using it in a virtualbox and it is running fine, except for the audio,
I can't make it work, do you have any workaround for it?
Thanks,
Cristian
--
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.
j***@gmail.com
2017-06-11 01:49:45 UTC
Permalink
First of all, Thank you for creating this wonderful 7.1 Nougat version for Android x86 project. I have successfully installed on my HP 608 G1 Tablet Cherry Trail X5 Z8500 processor. I can dual boot between Windows 10 and Android x86 Nougat now. There are couple of issue in this release which I hope the gurus could help me. I am not using this tablet for gaming, I just want to watch video and read some ebook and use Whatsapp.

Here is what not working and may required help:-
1. There is no sound. As far as HP tablet is concerned, the driver I see from Windows is Conexant I2S Audio Codec and Intel SST Audio Device (WDM). Is there away to add this driver in Android x86 and how ?

2. The battery indicator always shows 100% charged. If I don't plugged my power into my tablet before booting into Android, when it enters to the startup screen, it will poweroff by itself. To workaround this I have to plug in the power to my tablet at first startup. I just want to know if there is way to fix the battery information correctly ? Any pointers ?

3. The screen rotation is not working. I guess is due to the Accelerometer and Gyroscope is not functioning. That is fine, I don't need it as I download an app to perform the rotation manually. Thought of just telling you.

What I needed the most is the sound and battery fixed. I hope someone could help.

Here is the list what works in my HP 608 G1 tablet:-

1. Wifi
2. Bluetooth (Not stable, sometimes it keeps restarting)
3. Touchscreen
4. Power button and Volume button
5. Windows home button
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
j***@gmail.com
2017-06-11 15:34:30 UTC
Permalink
First of all, a big thank you for the team to make this project happen and you guys rock.

Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu) working with this release. I hope I'm not the first HP 608 G1 user who install this version because I hope someone or any guru that could provide some tips on issue that I am facing after installation.

A very quick test:
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works

What's not working and I believe is very important:
1. Sound not working. This tablet is using Intel SST. Using alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any SPO. Can anyone help me ? Do I need to recompile kernel to make this work ?

2. Power indicator is always showing 100% charged. This might or might not indirectly also causing my tablet to shutdown everytime i boot into the system. Unless I plug in my power in the beginning, otherwise, it will straight goes to shutdown mode.

3. Rotation is not working. Could be Accelerometer and Gyroscope is not, that is why. But no big issue, I can deal with it with manual rotation using 3rd party apps.

The first 2 issue is the most critical one. I hope someone could help me. OR give me some pointers where to look for solution. I have browse through the group, saw some alsa_amixer commands, or download AlsaMixer (Root), all not helping.

Your help is very much appreciated. I do hope to hear if any has successfully install this latest release Android x86 7.1 in their HP 608 G1

Thank you in advanced
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
j***@gmail.com
2017-06-13 03:20:42 UTC
Permalink
Thanks Chih-Wei. Will try Ubuntu and see if it helps. Thank you
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or might
not indirectly also causing my tablet to shutdown everytime i boot into the
system. Unless I plug in my power in the beginning, otherwise, it will
straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Joseph Lim
2017-06-18 20:41:19 UTC
Permalink
Hi Wei Huang,

I have installed Ubuntu 16.04.1 LTS, it doesn't have sound. I try to
understand more on the sound driver, therefore, I have tried my tablet in
Android x86 7.1 with the following command:-

$ alsa_aplay -l

**** List of PLAYBACK Hardware Devices ****
card 1: IntelHdmiLpeAud [IntelHdmiLpeAudio], device 0: IntelHdmiLpeAudio
[IntelHdmiLpeAudio]
Subdevices: 1/1
Subdevice #0: subdevice #0

It says card 1 found. Does that means the sound driver in loaded ? I have
noticed that my sound card is using Conexant and it requires CX2072 audio
codec. Does that means I need this codec in order for the sound to work ?

I have attached my Dmesg.txt, I saw alot of "avc: denied" messages. Will
that cause any problem ?
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or might
not indirectly also causing my tablet to shutdown everytime i boot into the
system. Unless I plug in my power in the beginning, otherwise, it will
straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Joseph Lim
2017-06-21 05:54:41 UTC
Permalink
Hi Wei Huang,

Any luck if you could add this patches into the latest kernel to support
Cherry Trail with Conexant CX2072 codec sound driver ?

https://github.com/CNXT-Jerry/CX2072X

There are discussion from this thread and kudos to Takashi and Pierre for
making this working on new tablet running Cherry Trail.

https://bugzilla.kernel.org/show_bug.cgi?id=115531

This
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or might
not indirectly also causing my tablet to shutdown everytime i boot into the
system. Unless I plug in my power in the beginning, otherwise, it will
straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-22 05:41:14 UTC
Permalink
available at
upstreamhttps://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/soc-cx2072x
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/soc-cx2072x-4.10
add these patches to 4.9should be no problem.
if you get sound work on desktop Linux by pluseaudio and ucm fileplease
you provide asound.state fileit is system/etc/alsa/chtcx2072x.state .

圚 2017幎6月22日星期四 UTC+8䞊午9:48:16Joseph Lim写道
Post by Joseph Lim
Hi Wei Huang,
Any luck if you could add this patches into the latest kernel to support
Cherry Trail with Conexant CX2072 codec sound driver ?
https://github.com/CNXT-Jerry/CX2072X
There are discussion from this thread and kudos to Takashi and Pierre for
making this working on new tablet running Cherry Trail.
https://bugzilla.kernel.org/show_bug.cgi?id=115531
This
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or
might not indirectly also causing my tablet to shutdown everytime i boot
into the system. Unless I plug in my power in the beginning, otherwise, it
will straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-22 06:08:29 UTC
Permalink
and clk: x86: add "mclk" alias for Baytrail/Cherrytrail
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/clk-cherrytrail

圚 2017幎6月22日星期四 UTC+8䞊午9:48:16Joseph Lim写道
Post by Joseph Lim
Hi Wei Huang,
Any luck if you could add this patches into the latest kernel to support
Cherry Trail with Conexant CX2072 codec sound driver ?
https://github.com/CNXT-Jerry/CX2072X
There are discussion from this thread and kudos to Takashi and Pierre for
making this working on new tablet running Cherry Trail.
https://bugzilla.kernel.org/show_bug.cgi?id=115531
This
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or
might not indirectly also causing my tablet to shutdown everytime i boot
into the system. Unless I plug in my power in the beginning, otherwise, it
will straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-22 05:31:55 UTC
Permalink
need these patches .
ASoC: cx2072x: Add DT bingings documentation for CX2072X CODEC
ASoC: add support for Conexant CX2072X CODEC
ASoC: Intel: Add machine driver for Cherrytrail-CX2072X
ASoC: Intel: add support for CX2072x machine driver
ASoC: cx2072x: Add missing declarations of jack detection helpers
ASoC: cx2072x: Fix missing DAPM entry definitions
ASoC: intel: Add headset jack support to cht-cx2072x
ASoC: cx2072x: Fix missing power hooks
ASoC: cx2072x: Workaround for the jack detection during cache-only
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/soc-cx2072x-4.10

圚 2017幎6月22日星期四 UTC+8䞊午9:48:16Joseph Lim写道
Post by Joseph Lim
Hi Wei Huang,
Any luck if you could add this patches into the latest kernel to support
Cherry Trail with Conexant CX2072 codec sound driver ?
https://github.com/CNXT-Jerry/CX2072X
There are discussion from this thread and kudos to Takashi and Pierre for
making this working on new tablet running Cherry Trail.
https://bugzilla.kernel.org/show_bug.cgi?id=115531
This
Post by j***@gmail.com
Post by j***@gmail.com
First of all, a big thank you for the team to make this project happen
and you guys rock.
Post by j***@gmail.com
Happy to see my HP 608 G1 tablet (Intel CherryTrail X5 Z8500 cpu)
working with this release. I hope I'm not the first HP 608 G1 user who
install this version because I hope someone or any guru that could provide
some tips on issue that I am facing after installation.
Post by j***@gmail.com
1. Wifi works
2. Touchscreen works
3. Brightness, power button and volume works
4. Video playback and Youtube works
1. Sound not working. This tablet is using Intel SST. Using
alsa_amixer -c 1, I only see Right Left Speaker, Mic. I didn't see any
SPO. Can anyone help me ? Do I need to recompile kernel to make this work
?
Probably there is no audio driver for this device,
or we didn't configure it correctly.
You may try to test a modern linux distribution
like ubuntu or fedora to see if it works.
If yes, figure out what driver it is.
Post by j***@gmail.com
2. Power indicator is always showing 100% charged. This might or
might not indirectly also causing my tablet to shutdown everytime i boot
into the system. Unless I plug in my power in the beginning, otherwise, it
will straight goes to shutdown mode.
Post by j***@gmail.com
3. Rotation is not working. Could be Accelerometer and Gyroscope is
not, that is why. But no big issue, I can deal with it with manual
rotation using 3rd party apps.
Ditto.
Post by j***@gmail.com
The first 2 issue is the most critical one. I hope someone could help
me. OR give me some pointers where to look for solution. I have browse
through the group, saw some alsa_amixer commands, or download AlsaMixer
(Root), all not helping.
Post by j***@gmail.com
Your help is very much appreciated. I do hope to hear if any has
successfully install this latest release Android x86 7.1 in their HP 608 G1
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
YoungJoon Lee
2017-06-11 03:44:17 UTC
Permalink
Thank you for release.

I test 7.1 yesterday. I cannot found NVMe SSD device on installer. I boot
with debug mode and found that nvmen1p1 is not present on /dev/.

So, I download and build nougat-x86 branch.
I set kernel with attached configuration file.

I tried boot with my iso file. But, there is no NVMe SSD. So, I push Detect
device menu. after few second, I can found there is my NVMe device. So, I
push partition which I want to install. But file system select is not
appeared and return to device select menu. there is no error message. I
boot with debug mode and check logs and else. First, dmesg said nvme module
is loaded without any errors. Second, I can found device on /dev/ but not
registered on /dev/block/.

Another issue is WIFI of ath10k. dmesg log said, same log of ubuntu(wifi
works).

<Loading Image...>

There is 2 errors about firmware but finally, board id is detected. There
logs are shown on ubuntu too. After boot, I can turn on wifi and wifi
setting said looking for ssid.(If WIFI module is not loaded, response of
wifi message is different.

I tried, change firmware file name to file name of error
message(firmware-5.bin) and place board1 and board2 file. And error message
said cannot specify board id.

This is my PC's environment.
MOBO : ASUS z270i strix
SSD : Samsung 960 evo NVMe SSD

Thank you for reading.

Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Doug McKeen
2017-06-14 15:56:22 UTC
Permalink
Nougat! Nice! and thanks.

I'm sometimes getting "shifted graphics" that I hadn't seen with previous android-x86 installs. My screen is shifted about 40% to the side (and wraps around the other side). Touches still work, but only where the item touched would normally be.

The shifted graphics seem to occur randomly...sometimes happening when rebooted from within Windows 10 and sometimes happening with a cold boot and sometimes the graphics work fine. There doesn't seem to be any consistency into when it happens.

When the shifted graphics does happen, it appears during the boot sequence. I can see it with some of the console output and then the "android" splash screen.

I'm using an Asus T100HA with Z3775 CPU and Intel HD Graphics.

Other hardware seems to be functioning similarly to that with android-x86 MM...(not working=brightness adjustment, auto brightness, camera, notification/camera light stuck on). Now working=volume and mute adjustments with keyboard dock and auto rotate!)

If I could only disable that stuck light and adjust the screen brightness I'd be using this all the time.

Thanks for nougat!
--
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.
Doug McKeen
2017-06-14 15:40:02 UTC
Permalink
Nougat! Nice! and thanks.

I'm sometimes getting "shifted graphics" that I hadn't seen with previous android-x86 installs. My screen is shifted about 40% to the side (and wraps around the other side). Touches still work, but only where the item touched would normally be.

The shifted graphics seem to occur randomly...sometimes happening when rebooted from within Windows 10 and sometimes happening with a cold boot and sometimes the graphics work fine. There doesn't seem to be any consistency into when it happens.

When the shifted graphics does happen, it appears during the boot sequence. I can see it with some of the console output and then the "android" splash screen.

I'm using an Asus T100HA with Z3775 CPU and Intel HD Graphics.

Other hardware seems to be functioning similarly to that with android-x86 MM...(not working=brightness adjustment, auto brightness, camera, notification/camera light stuck on). Now working=volume and mute adjustments with keyboard dock and auto rotate!)

If I could only disable that stuck light and adjust the screen brightness I'd be using this all the time.

Thanks for nougat!
--
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.
Povilas Staniulis
2017-06-15 12:20:41 UTC
Permalink
This post might be inappropriate. Click to display it.
Doug McKeen
2017-06-15 05:05:55 UTC
Permalink
I can just say the 32-bit image always works well,
but the 64-bit image has the same issue.
Post by Doug McKeen
Other hardware seems to be functioning similarly to that with
android-x86 MM...(not working=brightness adjustment, auto brightness,
camera, notification/camera light stuck on). Now working=volume and mute
adjustments with keyboard dock and auto rotate!)
Post by Doug McKeen
If I could only disable that stuck light and adjust the screen
brightness I'd be using this all the time.
Same on T100TA.
Honestly speaking I didn't notice brightness adjustment
doesn't work now. I thought it worked before.
Work: 4.4-r5 (kernel 4.0.9)
Not work: 6.0-r3 (kernel 4.4.62), 7.1-rc1 (kernel 4.9.31)
Need to survey what caused the regression.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Thanks. Trying the 32-bit image now.
--
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.
Ala'a Al-jabahji
2017-06-15 13:16:49 UTC
Permalink
Hi there,

thanks for your efforts to produce this image.

I've just had an issue, I'm trying to install android on my 2 in 1 mini
laptop (Acer One S1003)
until now i can't even boot to the system and every time stack on a black
screen or after boot there is no wireless option

could you please help me on this please?

regards,
Alaa
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Raymond Lai
2017-06-16 13:56:13 UTC
Permalink
I too wanted to use kernel 4.12 seeing hardware support is better. However
whenever I play videos, I got error messages from BufferQueueProducer and
SoftwareRenderer, saying things like

BufferQueueProducer: dequeueBuffer: attempting to exceed the max dequeued
buffer count (2)
SoftwareRenderer: Surface::dequeueBuffer returned error -38

Youtube, MX player both suffered from this, but not with kernel 4.9. Video
can play using software decoder in MX player instead.

I know this is not supported, but anyone else experienced this too on
mainline kernels? Perhaps problem with hardware video acceleration?

Device: GPD WIN (Z8700, 4GB, 64GB, brcm4356)
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-16 15:38:12 UTC
Permalink
To test this theory, you could open up a build.prop editor, and change
media.sf.hwaccel from 1 to 0. then reboot and see how video fares from there
Post by Raymond Lai
I too wanted to use kernel 4.12 seeing hardware support is better. However
whenever I play videos, I got error messages from BufferQueueProducer and
SoftwareRenderer, saying things like
BufferQueueProducer: dequeueBuffer: attempting to exceed the max dequeued
buffer count (2)
SoftwareRenderer: Surface::dequeueBuffer returned error -38
Youtube, MX player both suffered from this, but not with kernel 4.9. Video
can play using software decoder in MX player instead.
I know this is not supported, but anyone else experienced this too on
mainline kernels? Perhaps problem with hardware video acceleration?
Device: GPD WIN (Z8700, 4GB, 64GB, brcm4356)
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Raymond Lai
2017-06-17 13:27:23 UTC
Permalink
No go, still the same.

Maybe I should try the test build for Asus T100 posted in another thread
and see what happens... but that kernel seems missing some GPD WIN specific
patches to make wifi work... but anyway.
Post by Jon West
To test this theory, you could open up a build.prop editor, and change
media.sf.hwaccel from 1 to 0. then reboot and see how video fares from there
Post by Raymond Lai
I too wanted to use kernel 4.12 seeing hardware support is better.
However whenever I play videos, I got error messages from
BufferQueueProducer and SoftwareRenderer, saying things like
BufferQueueProducer: dequeueBuffer: attempting to exceed the max dequeued
buffer count (2)
SoftwareRenderer: Surface::dequeueBuffer returned error -38
Youtube, MX player both suffered from this, but not with kernel 4.9.
Video can play using software decoder in MX player instead.
I know this is not supported, but anyone else experienced this too on
mainline kernels? Perhaps problem with hardware video acceleration?
Device: GPD WIN (Z8700, 4GB, 64GB, brcm4356)
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Raymond Lai
2017-06-18 01:01:46 UTC
Permalink
I did another run with my own build and tried to see what dmesg said
instead. This time I saw something like this, when I switched back from
software to hardware decoder in MX player

avc: denied { read write } for pid=1528 comm="surfaceflinger"
path="/dev/dri/card0" dev="tmpfs" ino=8355 scontext=u:r:surfaceflinger:s0
tcontext=u:object_r:device:s0 tclass=chr_file permissive=1

Not sure if it's related, but seeing /dev/dri/card0 and surfaceflinger I
suppose this is the root of the problem?
Post by Raymond Lai
No go, still the same.
Maybe I should try the test build for Asus T100 posted in another thread
and see what happens... but that kernel seems missing some GPD WIN specific
patches to make wifi work... but anyway.
Post by Jon West
To test this theory, you could open up a build.prop editor, and change
media.sf.hwaccel from 1 to 0. then reboot and see how video fares from there
Post by Raymond Lai
I too wanted to use kernel 4.12 seeing hardware support is better.
However whenever I play videos, I got error messages from
BufferQueueProducer and SoftwareRenderer, saying things like
BufferQueueProducer: dequeueBuffer: attempting to exceed the max
dequeued buffer count (2)
SoftwareRenderer: Surface::dequeueBuffer returned error -38
Youtube, MX player both suffered from this, but not with kernel 4.9.
Video can play using software decoder in MX player instead.
I know this is not supported, but anyone else experienced this too on
mainline kernels? Perhaps problem with hardware video acceleration?
Device: GPD WIN (Z8700, 4GB, 64GB, brcm4356)
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Dondre Johnson
2017-06-17 23:42:06 UTC
Permalink
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Hello. Did you already support OTA updates?
- Support pages in Google Chrome app being in desktop mode by default
- Support Google+ app
- Support Zooming simulation (like in Remix OS, make the zoom shortcut Ctrl+Alt+mouse scroll)
--
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.
Slawomir Nowakowski
2017-06-16 12:51:33 UTC
Permalink
Hello all

No sound Realtek RT5640

Sorry for my language, my English isn’t good. I would like to change the system Windows 10 on my tablet to Android-x86 7.1-rc1, but I haven’t sound.
I would like change system because Windows 10 is very terrible on this device ( 1 GB RAM only ) . Android working very fast.
Processor Intel Atom Z3735G
WiFi Realtek RTL8723BS
Sound - Card-1 Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Card-2 bytcr-RT5640

I haven't problem with WiFi, bluetooth but sound not work.
Do you have any ideas how to fix this?
Thanks for help
--
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.
Dondre Johnson
2017-06-17 23:37:02 UTC
Permalink
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Hello. Were you able to support OTA updates?
- Support setting pages in Google Chrome in desktop mode by default
- Also support Google+ 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.
YoungJoon Lee
2017-06-16 15:57:03 UTC
Permalink
Hello, Chih-Wei. I have one more question. How can I install Gapps on
android-X86 build from source?

Thank you very much.
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-18 09:50:37 UTC
Permalink
YoungJoon Lee, you need to rebuild with built-in opengapps, check to these
instructions: https://github.com/opengapps/aosp_build
Post by YoungJoon Lee
Hello, Chih-Wei. I have one more question. How can I install Gapps on
android-X86 build from source?
Thank you very much.
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
YoungJoon Lee
2017-06-18 12:10:38 UTC
Permalink
Thank you very much. It is what I want. Have a Great weekend.
Post by Henri Koivuneva
YoungJoon Lee, you need to rebuild with built-in opengapps, check to these
instructions: https://github.com/opengapps/aosp_build
Post by YoungJoon Lee
Hello, Chih-Wei. I have one more question. How can I install Gapps on
android-X86 build from source?
Thank you very much.
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
YoungJoon Lee
2017-06-20 02:13:29 UTC
Permalink
Hello. I tried your link yesterday. receive next error.

[ 0% 29/27685] target Prebuilt: libfacenet (out/target/product
SHARED_LIBRARIES/libfacenet_intermediates/LINKED/libfacenet.so)
FAILED: /bin/bash -c "out/host/linux-x86/bin/acp -fp out/target/product/x86_64/obj/SHARED_LIBRARIES/libfacenet_intermediates/LINKED/libfacenet.so"
acp: missing destination file
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed.

How can I fix this error? I cannot found libfacenet.so.
I sync repo with --no-tags and --no-clone-bundle option.
YoungJoon Lee, you need to rebuild with built-in opengapps, check to these instructions: https://github.com/opengapps/aosp_build
Hello, Chih-Wei. I have one more question. How can I install Gapps on android-X86 build from source? 
Thank you very much.
2017년 6월 8음 목요음 였후 7시 23분 3쎈 UTC+9, Chih-Wei Huang 님의 말:Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
YoungJoon Lee
2017-06-20 10:40:03 UTC
Permalink
I also found that opengapps/aosp_also doesn't include libfacenet.so
Post by YoungJoon Lee
Hello. I tried your link yesterday. receive next error.
[ 0% 29/27685] target Prebuilt: libfacenet
(out/target/product
SHARED_LIBRARIES/libfacenet_intermediates/LINKED/libfacenet.so)
FAILED: /bin/bash -c "out/host/linux-x86/bin/acp -fp
out/target/product/x86_64/obj/SHARED_LIBRARIES/libfacenet_intermediates/LINKED/libfacenet.so"
acp: missing destination file
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed.
How can I fix this error? I cannot found libfacenet.so.
I sync repo with --no-tags and --no-clone-bundle option.
Post by Henri Koivuneva
YoungJoon Lee, you need to rebuild with built-in opengapps, check to
these instructions: https://github.com/opengapps/aosp_build
Post by Henri Koivuneva
Hello, Chih-Wei. I have one more question. How can I install Gapps on
android-X86 build from source?
Post by Henri Koivuneva
Thank you very much.
2017년 6월 8음 목요음 였후 7시 23분 3쎈 UTC+9, Chih-Wei Huang 님의 말:Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Joseph Lim
2017-06-18 17:29:04 UTC
Permalink
Do you guys have problem with Bluetooth ? My bluetooth is turning on and
off repeatedly. I have switch into Ubuntu and the bluetooth is working
fine. I have the dmesg for this 2 operating system. Can someone tell me
whats the problem ?

Android x86 7.1 (Non-Working Bluetooth, on and off repeatedly)
=================================================
x86_64:/ # dmesg | grep -i blue
[ 11.098330] Bluetooth: Core ver 2.22
[ 11.098458] Bluetooth: HCI device and connection manager initialized
[ 11.098473] Bluetooth: HCI socket layer initialized
[ 11.098514] Bluetooth: L2CAP socket layer initialized
[ 11.098584] Bluetooth: SCO socket layer initialized
[ 11.136940] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 11.163502] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 11.484266] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 12.547247] Bluetooth: HCI UART driver ver 2.3
[ 12.547252] Bluetooth: HCI UART protocol H4 registered
[ 12.547253] Bluetooth: HCI UART protocol BCSP registered
[ 12.547254] Bluetooth: HCI UART protocol LL registered
[ 12.547255] Bluetooth: HCI UART protocol ATH3K registered
[ 12.547256] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 12.547368] Bluetooth: HCI UART protocol Intel registered
[ 12.547406] Bluetooth: HCI UART protocol Broadcom registered
[ 12.547408] Bluetooth: HCI UART protocol QCA registered
[ 145.324571] type=1400 audit(1497806387.875:545): avc: denied { create }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325831] type=1400 audit(1497806387.876:546): avc: denied { bind }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325919] type=1400 audit(1497806387.876:547): avc: denied { write }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 145.325976] type=1400 audit(1497806387.876:548): avc: denied { read }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.026678] type=1400 audit(1497806440.578:593): avc: denied { create }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028873] type=1400 audit(1497806440.580:594): avc: denied { bind }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028989] type=1400 audit(1497806440.580:595): avc: denied { write }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.029050] type=1400 audit(1497806440.580:596): avc: denied { read }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 210.555713] type=1400 audit(1497806453.107:617): avc: denied { create }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 210.556782] type=1400 audit(1497806453.108:618): avc: denied { bind }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1

UBUNTU 16.04.2 LTS (Working Bluetooth)
=============================
***@PCPL003:~$ dmesg | grep -i blue
[ 7.134179] Bluetooth: Core ver 2.21
[ 7.134208] Bluetooth: HCI device and connection manager initialized
[ 7.134215] Bluetooth: HCI socket layer initialized
[ 7.134220] Bluetooth: L2CAP socket layer initialized
[ 7.134231] Bluetooth: SCO socket layer initialized
[ 7.160270] Bluetooth: HCI UART driver ver 2.3
[ 7.160273] Bluetooth: HCI UART protocol H4 registered
[ 7.160275] Bluetooth: HCI UART protocol BCSP registered
[ 7.160276] Bluetooth: HCI UART protocol LL registered
[ 7.160277] Bluetooth: HCI UART protocol ATH3K registered
[ 7.160278] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 7.160381] Bluetooth: HCI UART protocol Intel registered
[ 7.160414] Bluetooth: HCI UART protocol BCM registered
[ 7.160415] Bluetooth: HCI UART protocol QCA registered
[ 7.160416] Bluetooth: HCI UART protocol AG6XX registered
[ 7.542030] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 7.556469] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 7.928052] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 9.324399] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.324402] Bluetooth: BNEP filters: protocol multicast
[ 9.324408] Bluetooth: BNEP socket layer initialized
[ 21.209806] Bluetooth: RFCOMM TTY layer initialized
[ 21.209823] Bluetooth: RFCOMM socket layer initialized
[ 21.209844] Bluetooth: RFCOMM ver 1.11
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-06-19 13:42:25 UTC
Permalink
6.0 r3 and 7.1.2 rc1
[ 778.944698] Bluetooth: Non-link packet received in non-active state
[ 778.945175] Bluetooth: Non-link packet received in non-active state
[ 778.946828] Bluetooth: Non-link packet received in non-active state
[ 778.947578] Bluetooth: Out-of-order packet arrived (1 != 0)
[ 778.948973] Bluetooth: Non-link packet received in non-active state
[ 778.950030] Bluetooth: Out-of-order packet arrived (2 != 0)
[ 778.950047] Bluetooth: Non-link packet received in non-active state
[ 778.950059] Bluetooth: Non-link packet received in non-active state
[ 778.950070] Bluetooth: Non-link packet received in non-active state
[ 778.950080] Bluetooth: Non-link packet received in non-active state
[ 778.950091] Bluetooth: Non-link packet received in non-active state
[ 778.950551] Bluetooth: Non-link packet received in non-active state
[ 778.950939] Bluetooth: Out-of-order packet arrived (1 != 0)
[ 778.951927] Bluetooth: Out-of-order packet arrived (2 != 0)
[ 778.951947] Bluetooth: Out-of-order packet arrived (3 != 0)
[ 778.953638] Bluetooth: Non-link packet received in non-active state
[ 778.955859] Bluetooth: Non-link packet received in non-active state
[ 778.957955] Bluetooth: Non-link packet received in non-active state
[ 778.958552] Bluetooth: Out-of-order packet arrived (7 != 0)
[ 778.960112] Bluetooth: Non-link packet received in non-active state
[ 778.961476] Bluetooth: Non-link packet received in non-active state
[ 778.962367] Bluetooth: Non-link packet received in non-active state
[ 778.963037] Bluetooth: Out-of-order packet arrived (1 != 0)
[ 778.964543] Bluetooth: Non-link packet received in non-active state
[ 778.965221] Bluetooth: Out-of-order packet arrived (2 != 0)
[ 778.966845] Bluetooth: Non-link packet received in non-active state
[ 778.967295] Bluetooth: Out-of-order packet arrived (3 != 0)
[ 778.969023] Bluetooth: Non-link packet received in non-active state
[ 778.969420] Bluetooth: Out-of-order packet arrived (4 != 0)
[ 963.960810] Bluetooth: Out-of-order packet arrived (7 != 0)

圚 2017幎6月19日星期䞀 UTC+8䞊午10:21:09Joseph Lim写道
Post by Joseph Lim
Do you guys have problem with Bluetooth ? My bluetooth is turning on and
off repeatedly. I have switch into Ubuntu and the bluetooth is working
fine. I have the dmesg for this 2 operating system. Can someone tell me
whats the problem ?
Android x86 7.1 (Non-Working Bluetooth, on and off repeatedly)
=================================================
x86_64:/ # dmesg | grep -i blue
[ 11.098330] Bluetooth: Core ver 2.22
[ 11.098458] Bluetooth: HCI device and connection manager initialized
[ 11.098473] Bluetooth: HCI socket layer initialized
[ 11.098514] Bluetooth: L2CAP socket layer initialized
[ 11.098584] Bluetooth: SCO socket layer initialized
[ 11.136940] Bluetooth: hci0: read Intel version: 370810011003110e00
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 11.484266] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 12.547247] Bluetooth: HCI UART driver ver 2.3
[ 12.547252] Bluetooth: HCI UART protocol H4 registered
[ 12.547253] Bluetooth: HCI UART protocol BCSP registered
[ 12.547254] Bluetooth: HCI UART protocol LL registered
[ 12.547255] Bluetooth: HCI UART protocol ATH3K registered
[ 12.547256] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 12.547368] Bluetooth: HCI UART protocol Intel registered
[ 12.547406] Bluetooth: HCI UART protocol Broadcom registered
[ 12.547408] Bluetooth: HCI UART protocol QCA registered
[ 145.324571] type=1400 audit(1497806387.875:545): avc: denied { create }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325831] type=1400 audit(1497806387.876:546): avc: denied { bind }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325919] type=1400 audit(1497806387.876:547): avc: denied { write }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 145.325976] type=1400 audit(1497806387.876:548): avc: denied { read }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.026678] type=1400 audit(1497806440.578:593): avc: denied { create }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028873] type=1400 audit(1497806440.580:594): avc: denied { bind }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028989] type=1400 audit(1497806440.580:595): avc: denied { write }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.029050] type=1400 audit(1497806440.580:596): avc: denied { read }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 210.555713] type=1400 audit(1497806453.107:617): avc: denied { create }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 210.556782] type=1400 audit(1497806453.108:618): avc: denied { bind }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
UBUNTU 16.04.2 LTS (Working Bluetooth)
=============================
[ 7.134179] Bluetooth: Core ver 2.21
[ 7.134208] Bluetooth: HCI device and connection manager initialized
[ 7.134215] Bluetooth: HCI socket layer initialized
[ 7.134220] Bluetooth: L2CAP socket layer initialized
[ 7.134231] Bluetooth: SCO socket layer initialized
[ 7.160270] Bluetooth: HCI UART driver ver 2.3
[ 7.160273] Bluetooth: HCI UART protocol H4 registered
[ 7.160275] Bluetooth: HCI UART protocol BCSP registered
[ 7.160276] Bluetooth: HCI UART protocol LL registered
[ 7.160277] Bluetooth: HCI UART protocol ATH3K registered
[ 7.160278] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 7.160381] Bluetooth: HCI UART protocol Intel registered
[ 7.160414] Bluetooth: HCI UART protocol BCM registered
[ 7.160415] Bluetooth: HCI UART protocol QCA registered
[ 7.160416] Bluetooth: HCI UART protocol AG6XX registered
[ 7.542030] Bluetooth: hci0: read Intel version: 370810011003110e00
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 7.928052] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 9.324399] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.324402] Bluetooth: BNEP filters: protocol multicast
[ 9.324408] Bluetooth: BNEP socket layer initialized
[ 21.209806] Bluetooth: RFCOMM TTY layer initialized
[ 21.209823] Bluetooth: RFCOMM socket layer initialized
[ 21.209844] Bluetooth: RFCOMM ver 1.11
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
nassim moualek
2017-06-25 12:39:20 UTC
Permalink
Hi, i also have an Intel Bluetooth and i encountered the same problem, i
try to install the version 6 or 7 on VMBox or directly onmy Asus UX501V,
but the result is the same,
its connect and disconnect just after,i dont know how to read the log, it
seems i need to root the OS and dont know how to do it also, could you help
me to fix the issue, i am new to Androidx86.

Thanks
Post by Joseph Lim
Do you guys have problem with Bluetooth ? My bluetooth is turning on and
off repeatedly. I have switch into Ubuntu and the bluetooth is working
fine. I have the dmesg for this 2 operating system. Can someone tell me
whats the problem ?
Android x86 7.1 (Non-Working Bluetooth, on and off repeatedly)
=================================================
x86_64:/ # dmesg | grep -i blue
[ 11.098330] Bluetooth: Core ver 2.22
[ 11.098458] Bluetooth: HCI device and connection manager initialized
[ 11.098473] Bluetooth: HCI socket layer initialized
[ 11.098514] Bluetooth: L2CAP socket layer initialized
[ 11.098584] Bluetooth: SCO socket layer initialized
[ 11.136940] Bluetooth: hci0: read Intel version: 370810011003110e00
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 11.484266] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 12.547247] Bluetooth: HCI UART driver ver 2.3
[ 12.547252] Bluetooth: HCI UART protocol H4 registered
[ 12.547253] Bluetooth: HCI UART protocol BCSP registered
[ 12.547254] Bluetooth: HCI UART protocol LL registered
[ 12.547255] Bluetooth: HCI UART protocol ATH3K registered
[ 12.547256] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 12.547368] Bluetooth: HCI UART protocol Intel registered
[ 12.547406] Bluetooth: HCI UART protocol Broadcom registered
[ 12.547408] Bluetooth: HCI UART protocol QCA registered
[ 145.324571] type=1400 audit(1497806387.875:545): avc: denied { create }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325831] type=1400 audit(1497806387.876:546): avc: denied { bind }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325919] type=1400 audit(1497806387.876:547): avc: denied { write }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 145.325976] type=1400 audit(1497806387.876:548): avc: denied { read }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.026678] type=1400 audit(1497806440.578:593): avc: denied { create }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028873] type=1400 audit(1497806440.580:594): avc: denied { bind }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028989] type=1400 audit(1497806440.580:595): avc: denied { write }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.029050] type=1400 audit(1497806440.580:596): avc: denied { read }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 210.555713] type=1400 audit(1497806453.107:617): avc: denied { create }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 210.556782] type=1400 audit(1497806453.108:618): avc: denied { bind }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
UBUNTU 16.04.2 LTS (Working Bluetooth)
=============================
[ 7.134179] Bluetooth: Core ver 2.21
[ 7.134208] Bluetooth: HCI device and connection manager initialized
[ 7.134215] Bluetooth: HCI socket layer initialized
[ 7.134220] Bluetooth: L2CAP socket layer initialized
[ 7.134231] Bluetooth: SCO socket layer initialized
[ 7.160270] Bluetooth: HCI UART driver ver 2.3
[ 7.160273] Bluetooth: HCI UART protocol H4 registered
[ 7.160275] Bluetooth: HCI UART protocol BCSP registered
[ 7.160276] Bluetooth: HCI UART protocol LL registered
[ 7.160277] Bluetooth: HCI UART protocol ATH3K registered
[ 7.160278] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 7.160381] Bluetooth: HCI UART protocol Intel registered
[ 7.160414] Bluetooth: HCI UART protocol BCM registered
[ 7.160415] Bluetooth: HCI UART protocol QCA registered
[ 7.160416] Bluetooth: HCI UART protocol AG6XX registered
[ 7.542030] Bluetooth: hci0: read Intel version: 370810011003110e00
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 7.928052] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 9.324399] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.324402] Bluetooth: BNEP filters: protocol multicast
[ 9.324408] Bluetooth: BNEP socket layer initialized
[ 21.209806] Bluetooth: RFCOMM TTY layer initialized
[ 21.209823] Bluetooth: RFCOMM socket layer initialized
[ 21.209844] Bluetooth: RFCOMM ver 1.11
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Joseph Lim
2017-06-18 17:49:01 UTC
Permalink
Hi gurus,

My bluetooth is turning on and off repeatedly. I can see the bluetooth
able to search devices but then it turn off. I have installed Ubuntu
16.04.1 LTS on the same machine to test out and the bluetooth works just
fine. I have gathered some information. Do you know what is the issue ?
It looks like permission issue

Android x86 7.1 (Not working. Repeatedly turning on and off)
================================================
x86_64:/ # dmesg | grep -i blue
[ 11.098330] Bluetooth: Core ver 2.22
[ 11.098458] Bluetooth: HCI device and connection manager initialized
[ 11.098473] Bluetooth: HCI socket layer initialized
[ 11.098514] Bluetooth: L2CAP socket layer initialized
[ 11.098584] Bluetooth: SCO socket layer initialized
[ 11.136940] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 11.163502] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 11.484266] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 12.547247] Bluetooth: HCI UART driver ver 2.3
[ 12.547252] Bluetooth: HCI UART protocol H4 registered
[ 12.547253] Bluetooth: HCI UART protocol BCSP registered
[ 12.547254] Bluetooth: HCI UART protocol LL registered
[ 12.547255] Bluetooth: HCI UART protocol ATH3K registered
[ 12.547256] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 12.547368] Bluetooth: HCI UART protocol Intel registered
[ 12.547406] Bluetooth: HCI UART protocol Broadcom registered
[ 12.547408] Bluetooth: HCI UART protocol QCA registered
[ 145.324571] type=1400 audit(1497806387.875:545): avc: denied { create }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325831] type=1400 audit(1497806387.876:546): avc: denied { bind }
for pid=5342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 145.325919] type=1400 audit(1497806387.876:547): avc: denied { write }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 145.325976] type=1400 audit(1497806387.876:548): avc: denied { read }
for pid=5342 comm="hci_thread" path="socket:[69802]" dev="sockfs" ino=69802
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.026678] type=1400 audit(1497806440.578:593): avc: denied { create }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028873] type=1400 audit(1497806440.580:594): avc: denied { bind }
for pid=5960 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 198.028989] type=1400 audit(1497806440.580:595): avc: denied { write }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 198.029050] type=1400 audit(1497806440.580:596): avc: denied { read }
for pid=5960 comm="hci_thread" path="socket:[89576]" dev="sockfs" ino=89576
scontext=u:r:bluetooth:s0 tcontext=u:r:bluetooth:s0 tclass=socket
permissive=1
[ 210.555713] type=1400 audit(1497806453.107:617): avc: denied { create }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1
[ 210.556782] type=1400 audit(1497806453.108:618): avc: denied { bind }
for pid=6342 comm="hci_thread" scontext=u:r:bluetooth:s0
tcontext=u:r:bluetooth:s0 tclass=socket permissive=1


Ubuntu (Working)
====================
***@PCPL003:~$ dmesg | grep -i blue
[ 7.134179] Bluetooth: Core ver 2.21
[ 7.134208] Bluetooth: HCI device and connection manager initialized
[ 7.134215] Bluetooth: HCI socket layer initialized
[ 7.134220] Bluetooth: L2CAP socket layer initialized
[ 7.134231] Bluetooth: SCO socket layer initialized
[ 7.160270] Bluetooth: HCI UART driver ver 2.3
[ 7.160273] Bluetooth: HCI UART protocol H4 registered
[ 7.160275] Bluetooth: HCI UART protocol BCSP registered
[ 7.160276] Bluetooth: HCI UART protocol LL registered
[ 7.160277] Bluetooth: HCI UART protocol ATH3K registered
[ 7.160278] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 7.160381] Bluetooth: HCI UART protocol Intel registered
[ 7.160414] Bluetooth: HCI UART protocol BCM registered
[ 7.160415] Bluetooth: HCI UART protocol QCA registered
[ 7.160416] Bluetooth: HCI UART protocol AG6XX registered
[ 7.542030] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 7.556469] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 7.928052] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated
[ 9.324399] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.324402] Bluetooth: BNEP filters: protocol multicast
[ 9.324408] Bluetooth: BNEP socket layer initialized
[ 21.209806] Bluetooth: RFCOMM TTY layer initialized
[ 21.209823] Bluetooth: RFCOMM socket layer initialized
[ 21.209844] Bluetooth: RFCOMM ver 1.11
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
timyu via Android-x86
2017-06-19 00:52:47 UTC
Permalink
I encountered a problem that WeChat would display a black screen or simply crash upon openning. Release 6.0-r3 does not have this problem. I'm running android-x86_64-7.1-rc1 in VirtualBox with AMD APU.
--
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.
Hank Liao
2017-06-19 08:26:08 UTC
Permalink
Chih-Wei Huangæ–Œ 2017幎6月8日星期四 UTC+8䞋午6時23分03秒寫道
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Hello, using 7.1 rc1 on surface 3(non pro)and there is No sound

x86_64:/ # alsa_aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: IntelHdmiLpeAud [IntelHdmiLpeAudio], device 0: IntelHdmiLpeAudio [IntelHdmiLpeAudio]
Subdevices: 1/1
Subdevice #0: subdevice #0
here is dmesg: https://drive.google.com/file/d/0B924Ont99WuTWEc0X0pXNWRDLTg/view?usp=sharing
--
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.
Hank Liao
2017-06-20 03:24:51 UTC
Permalink
Chih-Wei Huangæ–Œ 2017幎6月20日星期二 UTC+8䞊午10時56分48秒寫道
Post by Joseph Lim
Post by Hank Liao
Hello, using 7.1 rc1 on surface 3(non pro)and there is No sound
x86_64:/ # alsa_aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: IntelHdmiLpeAud [IntelHdmiLpeAudio], device 0: IntelHdmiLpeAudio
[IntelHdmiLpeAudio]
Post by Hank Liao
Subdevices: 1/1
Subdevice #0: subdevice #0
https://drive.google.com/file/d/0B924Ont99WuTWEc0X0pXNWRDLTg/view?usp=sharing
Your kernel is mime but why your system is RemixOS,
as shown in cmdline?
BOOT_IMAGE=/RemixOS/kernel root=/dev/ram0 SERIAL=random
logo.showlogo=1 androidboot.selinux=permissive quiet DATA= SRC=RemixOS
CREATE_DATA_IMG=1
Did you just run RemixOS with replaced 7.1-rc1 kernel?
If so, you also need to copy /etc/alsa/chtrt5645.state
from 7.1-rc1.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
No I it just using remixos grub ,system.img data.img is 7.1 rc1 and it also
no sound when using usb live mode. Thank.
--
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.
Hank Liao
2017-06-20 03:16:23 UTC
Permalink
埞 Windows 10 的郵件傳送

寄件者: Chih-Wei Huang
傳送時間: 2017幎6月20日 䞊午 10:56
收件者: Android-x86
䞻旚: Re: Hello, using 7.1 rc1 on surface 3(non pro)and there is No sound
Post by Hank Liao
Hello, using 7.1 rc1 on surface 3(non pro)and there is No sound
x86_64:/ # alsa_aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: IntelHdmiLpeAud [IntelHdmiLpeAudio], device 0: IntelHdmiLpeAudio [IntelHdmiLpeAudio]
Subdevices: 1/1
Subdevice #0: subdevice #0
here is dmesg: https://drive.google.com/file/d/0B924Ont99WuTWEc0X0pXNWRDLTg/view?usp=sharing
Your kernel is mime but why your system is RemixOS,
as shown in cmdline?

BOOT_IMAGE=/RemixOS/kernel root=/dev/ram0 SERIAL=random
logo.showlogo=1 androidboot.selinux=permissive quiet DATA= SRC=RemixOS
CREATE_DATA_IMG=1

Did you just run RemixOS with replaced 7.1-rc1 kernel?
If so, you also need to copy /etc/alsa/chtrt5645.state
from 7.1-rc1.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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/gW95THsuqRw/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.

No I it just using remixos grub ,system.img data.img is 7.1 rc1 and it also no sound when using usb live mode. Thank.
講䞭文嗎
--
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.
Seis
2017-06-21 02:49:16 UTC
Permalink
I have a problem with my Surface 3. Everything worked fine for one day, but after I put my device to sleep I could not wake it up again. Even a restart doesnt work. My Device always restarts after detecting Android-X86. It only shows Android_ (before showing #-Symbol) and then restarts. Many 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.
youling 257
2017-06-22 06:16:40 UTC
Permalink
es8316 discussion at
herehttps://bugzilla.kernel.org/show_bug.cgi?id=189261#c79
--
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.
fguy
2017-08-15 22:37:54 UTC
Permalink
After updating to 7.1.2-r33, the brightness of the display is not adjusted
--
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.
fguy
2017-08-17 08:38:23 UTC
Permalink
четверг, 17 августа 2017 г., 5:13:56 UTC+3 пПльзПватель Chih-Wei Huang
I didn't see any explicit change that will affect
the brightness function.
Are you sure it works before 7.1.2-r33?
My last working build is 7.1.2-r27 x86_64 of 04.08
After updating to 7.1.2-r33 from 11.08, the brightness adjustment does not
work
I found the reason - the record is locked in
/sys/class/backlight/intel_backlight/brightness - in r27 I can write
another number there, see the change in brightness and read the recorded
number
I also did not find differences in the rights to this file between r27 and
r33 and the significant difference in files initrd.img and ramdisk.img
The last hope to do everything first from "repo init ..."
--
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.
fguy
2017-08-17 13:09:20 UTC
Permalink
Post by fguy
The last hope to do everything first from "repo init ..."
The "last hope" unfortunately did not come off - the "clean" build x86_64
behaves in exactly the same way
--
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.
fguy
2017-08-17 14:17:09 UTC
Permalink
The problem of writing to the file
"/sys/class/backlight/intel_backlight/brightness" turned out to be a
problem with the "Root Explorer 4.1.6" - in version 4.1.4 everything works
in 7.1.2-r33 - maybe the problem is in your changes to the libsync
--
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.
fguy
2017-08-17 18:55:35 UTC
Permalink
BINGO -Viva LOS 14.1 - problem
this https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/9f7f27a512629626e81bcb9233b28e1c2f90cef9
--
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-08-17 19:00:37 UTC
Permalink
can't adjust brightness by quick setting slider

only can adjust brightness by echo

android_x86:/ $ su
android_x86:/ # echo 30 >
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DSI-1/intel_backlight/brightness
android_x86:/ #
圚 2017幎8月18日星期五 UTC+8䞊午2:55:36fguy写道
BINGO -Viva LOS 14.1 - problem this
https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/9f7f27a512629626e81bcb9233b28e1c2f90cef9
--
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.
fguy
2017-08-18 06:30:53 UTC
Permalink
I do not understand the purpose of this patch - with respect to aosp, both
options when going to sleep and back behave the same way - where should the
incorrect mashing of the screen occur?

пятМОца, 18 августа 2017 г., 7:15:27 UTC+3 пПльзПватель Chih-Wei Huang
Post by fguy
BINGO -Viva LOS 14.1 - problem this
https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/9f7f27a512629626e81bcb9233b28e1c2f90cef9
Fine!
The patch is forward ported from lollipop-x86
but I didn't notice the applyGlobalDisplayStateLocked
(formly updateGlobalDisplayStateLocked)
function now also control brightness.
I've pushed a fix that works for me.
Please verify it.
Thank you for finding the bug.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
fguy
2017-08-18 06:32:42 UTC
Permalink
I do not understand the purpose of this patch - with respect to aosp, both
options when going to sleep and back behave the same way - where should the
incorrect mashing of the screen occur?

пятМОца, 18 августа 2017 г., 7:15:27 UTC+3 пПльзПватель Chih-Wei Huang
Post by fguy
BINGO -Viva LOS 14.1 - problem this
https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/9f7f27a512629626e81bcb9233b28e1c2f90cef9
Fine!
The patch is forward ported from lollipop-x86
but I didn't notice the applyGlobalDisplayStateLocked
(formly updateGlobalDisplayStateLocked)
function now also control brightness.
I've pushed a fix that works for me.
Please verify it.
Thank you for finding the bug.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
fguy
2017-08-18 06:59:58 UTC
Permalink
I do not understand the purpose of this patch.
With respect to aosp, both options when going to sleep and back behave the
same way.
Where should the incorrect mashing of the screen occur?

пятМОца, 18 августа 2017 г., 7:15:27 UTC+3 пПльзПватель Chih-Wei Huang
Post by fguy
BINGO -Viva LOS 14.1 - problem this
https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/9f7f27a512629626e81bcb9233b28e1c2f90cef9
Fine!
The patch is forward ported from lollipop-x86
but I didn't notice the applyGlobalDisplayStateLocked
(formly updateGlobalDisplayStateLocked)
function now also control brightness.
I've pushed a fix that works for me.
Please verify it.
Thank you for finding the bug.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-08-17 18:43:23 UTC
Permalink
DisplayManagerService: disable display blanking on suspend lead to can't
adjust brightness.

圚 2017幎8月17日星期四 UTC+8䞊午10:13:56Chih-Wei Huang写道
Post by fguy
Post by fguy
After updating to 7.1.2-r33, the brightness of the display is not
adjusted
Hmm, strange.
I didn't see any explicit change that will affect
the brightness function.
Are you sure it works before 7.1.2-r33?
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-08-17 19:02:55 UTC
Permalink
can't adjust brightness by quick setting slider

only can adjust brightness by echo

无法通过快捷讟眮滑块滑劚调节屏幕亮床
只胜通过echo调节亮床

圚 2017幎8月17日星期四 UTC+8䞊午10:13:56Chih-Wei Huang写道
Post by fguy
Post by fguy
After updating to 7.1.2-r33, the brightness of the display is not
adjusted
Hmm, strange.
I didn't see any explicit change that will affect
the brightness function.
Are you sure it works before 7.1.2-r33?
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Phil Buck
2017-08-17 19:38:17 UTC
Permalink
Hi, All I Was Hoping To Build A Android Based Car PC, I Was Able To Set
The Power Button To Sleep But As Your See Im Having Issues With Sleep When
Usb Devices Are Connected, The Video Will Explain All


As The Video Shows The System Sleeps When The Touch Panel Is (Unplugged)
But When I Connect It (It Only Seems To Act Like A Lock Screen)

Yet The Same System Works (All Connected) With Previous Versions ... Hope
This Helps & Gets Resolved Promptly
http://youtu.be/FgC2W2Z4OD0

Again Keep Up The Good Work & Thought I Share The Problems I Have Come
Across
--
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-08-17 20:01:56 UTC
Permalink
did you edit build.propsleep.earlysuspend=1 ? make sure it enter suspend
s3 or s0 idle ?

圚 2017幎8月18日星期五 UTC+8䞊午3:38:17Phil Buck写道
Hi, All I Was Hoping To Build A Android Based Car PC, I Was Able To Set
The Power Button To Sleep But As Your See Im Having Issues With Sleep When
Usb Devices Are Connected, The Video Will Explain All
http://youtu.be/FgC2W2Z4OD0
As The Video Shows The System Sleeps When The Touch Panel Is (Unplugged)
But When I Connect It (It Only Seems To Act Like A Lock Screen)
Yet The Same System Works (All Connected) With Previous Versions ... Hope
This Helps & Gets Resolved Promptly
http://youtu.be/FgC2W2Z4OD0
Again Keep Up The Good Work & Thought I Share The Problems I Have Come
Across
--
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.
Phil Buck
2017-08-17 20:14:21 UTC
Permalink
Hi, I Was Advised To Enter The Following (In Build Prop) - Hence It Sleeps
(With No Prompt)

Poweroff.doubleclick=1 & sleep.earlysuspend=1 - But This Did Nothing

I Changed It To poweroff.doubleclick=1 & sleep.earlysuspend=2 - This Worked
(Kind Of) & As You See It In The Video..

I Will Again Try Changing The The 2 Back To 1 On Early Suspend & See What
It Does

This Mother Board Does Support A Range Of Power Saving Options

Like CPU C States Support (Its Set To C1)
Deep Sleep Is Also Disabled (As I Found In Older Android Versions It Turns
The Usb Power Off & Everytime It Would Wake I Get Them Annoying Boxes
Saying Device Found Open With Default App) Everytime So Kept It Disabled

Thanks For Your Reply & Hope The Video Explains The Issue Im Having
Post by youling 257
did you edit build.propsleep.earlysuspend=1 ? make sure it enter suspend
s3 or s0 idle ?
圚 2017幎8月18日星期五 UTC+8䞊午3:38:17Phil Buck写道
Hi, All I Was Hoping To Build A Android Based Car PC, I Was Able To Set
The Power Button To Sleep But As Your See Im Having Issues With Sleep When
Usb Devices Are Connected, The Video Will Explain All
http://youtu.be/FgC2W2Z4OD0
As The Video Shows The System Sleeps When The Touch Panel Is (Unplugged)
But When I Connect It (It Only Seems To Act Like A Lock Screen)
Yet The Same System Works (All Connected) With Previous Versions ... Hope
This Helps & Gets Resolved Promptly
http://youtu.be/FgC2W2Z4OD0
Again Keep Up The Good Work & Thought I Share The Problems I Have Come
Across
--
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/gW95THsuqRw/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-08-17 20:31:11 UTC
Permalink
YesBraswell J3160similar to Cherry trailshould be support “echo freeze >
/sys/power/state”

圚 2017幎8月18日星期五 UTC+8䞊午4:14:34Phil Buck写道
Post by Phil Buck
Hi, I Was Advised To Enter The Following (In Build Prop) - Hence It Sleeps
(With No Prompt)
Poweroff.doubleclick=1 & sleep.earlysuspend=1 - But This Did Nothing
I Changed It To poweroff.doubleclick=1 & sleep.earlysuspend=2 - This
Worked (Kind Of) & As You See It In The Video..
I Will Again Try Changing The The 2 Back To 1 On Early Suspend & See What
It Does
This Mother Board Does Support A Range Of Power Saving Options
Like CPU C States Support (Its Set To C1)
Deep Sleep Is Also Disabled (As I Found In Older Android Versions It Turns
The Usb Power Off & Everytime It Would Wake I Get Them Annoying Boxes
Saying Device Found Open With Default App) Everytime So Kept It Disabled
Thanks For Your Reply & Hope The Video Explains The Issue Im Having
Post by youling 257
did you edit build.propsleep.earlysuspend=1 ? make sure it enter suspend
s3 or s0 idle ?
圚 2017幎8月18日星期五 UTC+8䞊午3:38:17Phil Buck写道
Hi, All I Was Hoping To Build A Android Based Car PC, I Was Able To Set
The Power Button To Sleep But As Your See Im Having Issues With Sleep When
Usb Devices Are Connected, The Video Will Explain All
http://youtu.be/FgC2W2Z4OD0
As The Video Shows The System Sleeps When The Touch Panel Is (Unplugged)
But When I Connect It (It Only Seems To Act Like A Lock Screen)
Yet The Same System Works (All Connected) With Previous Versions ...
Hope This Helps & Gets Resolved Promptly
http://youtu.be/FgC2W2Z4OD0
Again Keep Up The Good Work & Thought I Share The Problems I Have Come
Across
--
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/gW95THsuqRw/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.
Phil Buck
2017-08-17 20:34:39 UTC
Permalink
How To I Add/Edit The System To Fix This, Should It Work Will Give You A
Mention On A Youtube Video (When Ive Done A Full Build VIdeo)
Is This Something I Need To Add In "build prop Editor"

Thanks Again For Your Help & Time Replying :)
Post by youling 257
YesBraswell J3160similar to Cherry trailshould be support “echo freeze
Post by youling 257
/sys/power/state”
圚 2017幎8月18日星期五 UTC+8䞊午4:14:34Phil Buck写道
Post by youling 257
Hi, I Was Advised To Enter The Following (In Build Prop) - Hence It
Sleeps (With No Prompt)
Poweroff.doubleclick=1 & sleep.earlysuspend=1 - But This Did Nothing
I Changed It To poweroff.doubleclick=1 & sleep.earlysuspend=2 - This
Worked (Kind Of) & As You See It In The Video..
I Will Again Try Changing The The 2 Back To 1 On Early Suspend & See What
It Does
This Mother Board Does Support A Range Of Power Saving Options
Like CPU C States Support (Its Set To C1)
Deep Sleep Is Also Disabled (As I Found In Older Android Versions It
Turns The Usb Power Off & Everytime It Would Wake I Get Them Annoying Boxes
Saying Device Found Open With Default App) Everytime So Kept It Disabled
Thanks For Your Reply & Hope The Video Explains The Issue Im Having
Post by youling 257
did you edit build.propsleep.earlysuspend=1 ? make sure it enter
suspend s3 or s0 idle ?
圚 2017幎8月18日星期五 UTC+8䞊午3:38:17Phil Buck写道
Hi, All I Was Hoping To Build A Android Based Car PC, I Was Able To Set
The Power Button To Sleep But As Your See Im Having Issues With Sleep When
Usb Devices Are Connected, The Video Will Explain All
http://youtu.be/FgC2W2Z4OD0
As The Video Shows The System Sleeps When The Touch Panel Is
(Unplugged) But When I Connect It (It Only Seems To Act Like A Lock Screen)
Yet The Same System Works (All Connected) With Previous Versions ...
Hope This Helps & Gets Resolved Promptly
http://youtu.be/FgC2W2Z4OD0
Again Keep Up The Good Work & Thought I Share The Problems I Have Come
Across
--
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/gW95THsuqRw/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-08-17 20:05:56 UTC
Permalink
BYT/CHTit is s2idle

android_x86:/ $ su
android_x86:/ # cat /sys/power/mem_sleep
[s2idle]
android_x86:/ # cat /sys/power/state
freeze mem
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.
Phil Buck
2017-08-17 20:25:13 UTC
Permalink
I Think Your Correct Strangely With The Touch Screen Connected Its Only
Going In To S2Idle (Not Sleep As It Does Unconnected)

Just Changed The Sleep.earlysuspend=1 (But Again It Does Nothing) Happens
As Before... (Nothing What So Ever)

Could You Tell Me How I Go About Adding Code You Mentioned Earlier, Thanks
:)
Post by youling 257
BYT/CHTit is s2idle
android_x86:/ $ su
android_x86:/ # cat /sys/power/mem_sleep
[s2idle]
android_x86:/ # cat /sys/power/state
freeze mem
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.
youling 257
2017-08-17 20:35:04 UTC
Permalink
please you connect touchscreensuspend/resumecompare dmesg with disconnect
touchscreen

圚 2017幎8月18日星期五 UTC+8䞊午4:25:13Phil Buck写道
Post by Phil Buck
I Think Your Correct Strangely With The Touch Screen Connected Its Only
Going In To S2Idle (Not Sleep As It Does Unconnected)
Just Changed The Sleep.earlysuspend=1 (But Again It Does Nothing) Happens
As Before... (Nothing What So Ever)
Could You Tell Me How I Go About Adding Code You Mentioned Earlier, Thanks
:)
Post by youling 257
BYT/CHTit is s2idle
android_x86:/ $ su
android_x86:/ # cat /sys/power/mem_sleep
[s2idle]
android_x86:/ # cat /sys/power/state
freeze mem
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.
Greg McGee
2017-08-20 07:42:46 UTC
Permalink
Thank you sir, this is working ~usably on my old Lenovo X200T in 32 bit.
with 64 bit, mesa seems to crash immediately, zygote crashes and reloads
endlessly.

Sleep, sound, wifi, network (ethernet) all work.

The bluetooth turns on then the service dies, lather rinse repeat.
video doesn't play, black screens for video in youtube no crashes (old
Intel gfx chipset GM45)

The serial Wacom pen nominally works, but it works in relative mode (like a
touchpad) and the calibration is off, thats really the only thing keeping
it from being 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.
Carlos Junior
2017-08-20 13:42:36 UTC
Permalink
It works with my nvidia 1060gtx gpu I am using it in my razer blade 2016
verseion qhd touchscreen but I have no sound, no microphone and no camera
working. Please make them work. I have found linux drivers for Realtek high
def audio that my razer blade 2016 uses please add this to the sourc of the
android x86. Thanks for all your hard work to make android 7.1 possible to
use for us.

http://www.realtek.com.tw/downloads/downloadsview.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Ted Seventy
2017-09-24 23:58:48 UTC
Permalink
hello guys,
why is my Nougat build smaller than the prebuilt ISO ? The prebuilt "
android-x86_64-7.1-rc1.iso
<https://osdn.net/projects/android-x86/downloads/67834/android-x86_64-7.1-rc1.iso/>"
is 785MB, but my build is only 535MB. I followed exactly the build process
from here;
http://www.android-x86.org/getsourcecode

My build when boot up, will ask me to choose launcher or desktop, and it's
missing Messaging app (and possibly telephony, RIL). The prebuilt image is
asking to setup the "phone". How do I make a build exactly like that ?

thank you in advance!

-Ted
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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-09-25 01:30:28 UTC
Permalink
Did you include opengapps in it? Sounds like they might be missing. You can
find information on that here:
https://github.com/opengapps/aosp_build

After following the guide there and adding the repos to your manifest and
required parts in your config files, do these commands again in Android-x86
folder:
1. "repo sync --no-tags --no-clone-bundle"

make a new clean build
2. "make clean"
3. ". build/envsetup.sh"
4. "lunch YOURDEVICE", example: "lunch android_x86_64-userdebug"
5. "time m -jX iso_img" / "m -jX iso_img", example: "time make -j8 iso_img"

Hope this helps. Good luck!
Post by Ted Seventy
hello guys,
why is my Nougat build smaller than the prebuilt ISO ? The prebuilt "
android-x86_64-7.1-rc1.iso
<https://osdn.net/projects/android-x86/downloads/67834/android-x86_64-7.1-rc1.iso/>"
is 785MB, but my build is only 535MB. I followed exactly the build process
from here;
http://www.android-x86.org/getsourcecode
My build when boot up, will ask me to choose launcher or desktop, and it's
missing Messaging app (and possibly telephony, RIL). The prebuilt image is
asking to setup the "phone". How do I make a build exactly like that ?
thank you in advance!
-Ted
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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/gW95THsuqRw/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.
Ted Seventy
2017-09-25 03:06:55 UTC
Permalink
Thanks man! I didn't do opengapps part. I'll try it tonight and cross my
fingers :-)

-ted
Post by Henri Koivuneva
Did you include opengapps in it? Sounds like they might be missing. You
https://github.com/opengapps/aosp_build
After following the guide there and adding the repos to your manifest and
required parts in your config files, do these commands again in Android-x86
1. "repo sync --no-tags --no-clone-bundle"
make a new clean build
2. "make clean"
3. ". build/envsetup.sh"
4. "lunch YOURDEVICE", example: "lunch android_x86_64-userdebug"
5. "time m -jX iso_img" / "m -jX iso_img", example: "time make -j8 iso_img"
Hope this helps. Good luck!
Post by Ted Seventy
hello guys,
why is my Nougat build smaller than the prebuilt ISO ? The prebuilt "
android-x86_64-7.1-rc1.iso
<https://osdn.net/projects/android-x86/downloads/67834/android-x86_64-7.1-rc1.iso/>"
is 785MB, but my build is only 535MB. I followed exactly the build process
from here;
http://www.android-x86.org/getsourcecode
My build when boot up, will ask me to choose launcher or desktop, and
it's missing Messaging app (and possibly telephony, RIL). The prebuilt
image is asking to setup the "phone". How do I make a build exactly like
that ?
thank you in advance!
-Ted
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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/gW95THsuqRw/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.
Suresh Kumar
2017-10-06 12:52:10 UTC
Permalink
Post by Ted Seventy
Thanks man! I didn't do opengapps part. I'll try it tonight and cross my
fingers :-)
-ted
Post by Henri Koivuneva
Did you include opengapps in it? Sounds like they might be missing. You
https://github.com/opengapps/aosp_build
After following the guide there and adding the repos to your manifest and
required parts in your config files, do these commands again in Android-x86
1. "repo sync --no-tags --no-clone-bundle"
make a new clean build
2. "make clean"
3. ". build/envsetup.sh"
4. "lunch YOURDEVICE", example: "lunch android_x86_64-userdebug"
5. "time m -jX iso_img" / "m -jX iso_img", example: "time make -j8 iso_img"
Hope this helps. Good luck!
Post by Ted Seventy
hello guys,
why is my Nougat build smaller than the prebuilt ISO ? The prebuilt "
android-x86_64-7.1-rc1.iso
<https://osdn.net/projects/android-x86/downloads/67834/android-x86_64-7.1-rc1.iso/>"
is 785MB, but my build is only 535MB. I followed exactly the build process
from here;
http://www.android-x86.org/getsourcecode
My build when boot up, will ask me to choose launcher or desktop, and
it's missing Messaging app (and possibly telephony, RIL). The prebuilt
image is asking to setup the "phone". How do I make a build exactly like
that ?
thank you in advance!
-Ted
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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/gW95THsuqRw/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.
We are facing compilation problem in external/mesa directory, after
latest code change of 3 oct 17.



Also, there are

1.No options like :- repo init -u <address> -b refs/tags/<tagname> -m
version.xml

2. No tags



Please give us a option like above, to do sync for older version of
nougat-x86,

Regards,

Suresh
--
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.
Suresh Kumar
2017-10-06 12:52:42 UTC
Permalink
We are facing compilation problem in external/mesa directory, after latest
code change of 3 oct 17.



Also, there are

1.No options like :- repo init -u <address> -b refs/tags/<tagname> -m
version.xml

2. No tags



Please give us a option like above, to do sync for older version of
nougat-x86,

Regards,

Suresh
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
Suresh Kumar
2017-10-09 06:54:06 UTC
Permalink
Its now resolved .
But it will be better ,if we can have a specific TAG for current repository.
Post by Suresh Kumar
We are facing compilation problem in external/mesa directory, after latest
code change of 3 oct 17.
Also, there are
1.No options like :- repo init -u <address> -b refs/tags/<tagname> -m
version.xml
2. No tags
Please give us a option like above, to do sync for older version of
nougat-x86,
Regards,
Suresh
Hi all,
After about 11 months of development,
we are able to release the first rc of 7.1 (nougat-x86).
It's longer than I expected. But finally we did it.
By using latest LTS kernel 4.9.31 and Mesa 17.1.2,
we are able to support more devices and peripherals.
The most significant improvement of this release
is the hardware accelerated codecs support
on devices with Intel HD graphics family.
This reduces the CPU usage on playing video.
On an device with Intel core i3 or better
we can play 4K video smoothly.
Please see VAAPI doc to see
https://github.com/01org/intel-vaapi-driver/blob/master/README
Besides, with the latest ffmpeg plugins
we are able to play almost all video files.
Hope you enjoy it!
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
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.
e***@gmail.com
2017-11-26 22:30:32 UTC
Permalink
Anyone having issues with the YouTube app crashing?
--
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...