Android x86_64 7.1.1 Iso File Release?

[orha...@gmail.com]

Android x86_64 7.1.1 Iso File Release?

[Harkaman Shivakoti]

I don't think so. But u can try  version: 7.1-rc0 from, https://www.fosshub.com/Android-x86.html

[dgdn]

UNOFFICIAL most recent test builds are usually here:

https://drive.google.com/drive/folders/0B3Vjym21YjOTTERmbk1MZjJ6Ylk?usp=sharing

[Midi Jari]

do they have gapps implemented?

[Larry Underhill]

looks pretty good. any luck on rooting?

[Larry Underhill]

Yes just read the .docx file basically manually setting permissions.

[dgdn]

me thinks rooting on NOUGAT sort of defeats the goal of Google in having a more secure release, as I recall

Apps that need root / etc. are granted such based on Security Policy, and any rooting would defeat the purpose....

However, if you build an engineering build the developer options should allow rooting when available / debugged for
android-x86......IMO

[dgdn]

"Let's start at the beginning — this isn't about the Pixel phones, it's about Android 7.0."

http://www.androidcentral.com/android-and-chill-nougat-and-root-question

[Mike]

Lol

Sent with AquaMail for Android
http://www.aqua-mail.com

--
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 andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[dgdn]

excellent work by the developers at Evervolv & xda.....in the last two weeks I have installed

Nougat 7.1.1 on my 5 year old HP Touchpad (Qualcomm snapdragon ARM processor)

http://forum.xda-developers.com/hp-touchpad/help/how-to-install-android-7-x-hp-touchpad-t3512182

also added marshmallow to my other HP Touchpad......both work super..........

http://forum.xda-developers.com/showthread.php?t=2321397

many new tools that simplify all I had learned back in 2011-2012 with the touchpad

[Mauro Rossi]

Il giorno martedì 13 dicembre 2016 15:17:45 UTC+1, orha...@gmail.com ha scritto:

Android x86_64 7.1.1 Iso File Release?

7.1.1.r6 experimental ISOs at the following link:

https://drive.google.com/drive/folders/0B_OFHiIqgpSFMlk4bkhaMnAwbDA?usp=sharing

Please consider that in order to have a working debug mode the attached patch was applied to frameworks/base project
Mauro

[Jan Cervenka]

Hi - I am having problems booting your nougat 7.1 builds with 4.9 kernel.

Can you help?

Thanks

[Mauro Rossi]

Il giorno mercoledì 28 dicembre 2016 22:07:32 UTC+1, Jan Cervenka ha scritto:

Hi - I am having problems booting your nougat 7.1 builds with 4.9 kernel.

Can you help?

Thanks

Hi Jan, me too...

I know about the following issues (all kernel-4.4 vd kernel-4.9 independent):

1) installing on (S)ATA hard disk is somehow problematic and leads to a non repeateable boot, while booting LiveCD is usually working (but is one-shot)

2) radeonsi is booting, with a modified version of LLVM 3.8.0 "plus AMDGPU target", but  I cannot complete the sign-in (the problem seems related to EGLterminate causing a systematic SIGSEGV MAPERR)

3) latest mesa-dev EGLswapBufferWithDamage patches had to be reverted because it prevents AssetAtlas loading

It seams also that reverting those patches like done in https://github.com/maurossi/mesa prevents some nouveau freezes

I think you are referring to issue n.1), but please provide some information on your system and happenings, and if possible dmesg and logcat

In my understanding the installation has issues independendent from kernel-4.9, but I was unable to understand the cause yet.

I'd also like some feedback from other people who tried the installation of the the stock 7.1.1r4

(no DEBUG mode, because it is currently flawed by a show stopper issue, due to recent framework/base whitelists enforcements affecting the chroot mechanism used in dEBUG mode)

Mauro

[Jan Cervenka]

Hi

My issue is probably 1) like you said. It is installed on a parition the Surface Pro 3 sata ssd disk. The partition is formatted to EXT4. When the installer is complete and I select boot now it does boot in. As soon as I reboot I can get it to boot again. Booting live CD works just fine. Are these Files any help? I am not sure I got the logcat / dmesg right. If not please tell me how to retrieve them and I will do that.

Thanks for your help! 

[Wesley Henrique]

Wtf Androi-x86 7.1.1 RC0 very stable.

[Henri Koivuneva]

 I guess you have GRUB installed? Do you also have Ubuntu and Windows? I also had issues with installing to EXT4, so I'm using them as .img instead of installed to partitions. That blocks me from editing the system partition and rooting (I guess) and such but I don't really need to do that stuff.. If I need some changes, I'll just build a new image after editing the source with the needed mods.

I have the Android boot set up this way, my Nougat build as the example, with a 4GB data img created in Ubuntu (rename it from data-4gb.img to data.img).

Partition layout on my Surface Pro 3 internal SSD (to see why I point to sda3 in grub 40_custom config):

/dev/sda1 --  200M -- EFI System
/dev/sda2 --  128M -- Microsoft reserved
/dev/sda3 --   46G -- Windows 10 (this is where my Android images are too)
/dev/sda4 --    2G -- Bitlocker partition for work files
/dev/sda5 --  488M -- Linux swap
/dev/sda6 -- 10,4G -- Ubuntu
/dev/sda7 --  450M -- Windows recovery

This is how I did it on my SP3:
1. Make a folder in Windows C:\ partition called "nougat" so the path is C:\nougat

2. Copy the images there, so that the paths are for example c:\nougat\system.sfs & c:\nougat\initrd.img & c:\nougat\data.img

3. in Ubuntu terminal, do:

sudo gedit /etc/grub.d/40_custom

4. Paste the following to the end of the file (change the set root='sda3' part to point to your own partition, it can be ext4 or ntfs..if you use ext4 you can remove the insmod ntfs line):

menuentry 'Nougat-x86' --class android-x86 {
    insmod part_gpt
    insmod ntfs
    set root='sda3'
    set DIR=/nougat
    search --file --no-floppy --set=root $DIR/system.sfs
    linux $DIR/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=$DIR/data.img
    initrd $DIR/initrd.img
}

5. Save the file and close the text editor

6. Do:

sudo update-grub

7. Reboot and test if it worked. If yes, you should boot to android! Note that you'll need a data.img file OR a "data" folder in the ext4 partition for your data, settings, apps etc. to be saved. If you make it a folder called data inside the nougat folder (path nougat/data) it should work, provided that the folder is inside an ext4 partition... but permission issues might arise so that's why I use a data.img file.

8. If you want to resize the 4GB data.img I linked above, to for example 16GB, open terminal in the nougat folder and do these commands:

e2fsck -f data.img
resize2fs data.img 16G
e2fsck -f data.img

9. I've found those commands to be safe for the data inside that image. Just make sure you don't make it smaller than the actual data that's in there, for example if you have 13.7GB of apps and data etc. in there I wouldn't resize it below 16GB.

10. When you want to update the system to a new version, for example when a new official build comes, you only need to replace the image files below and leave your data.img intact:

initrd.img
kernel
ramdisk.img
system.sfs

This way your data will stay but system will be updated! Fast, easy and pretty much hassle-free at least in my experience. If you switch between CyanogenMod/LineageOS and default Android-x86, I'd recommend to keep separate data.img files.

It's also possible to run it from an SD card or USB media this way but they're of course much slower unless they're SSDs too.

The only downside in using GRUB is that I have found no way to make it work with the touch screen so every time I want to choose a different option than the default, I need to attach the keyboard. It's quite a small annoyance though. I haven't had time to try rEFInd or Clover for linux/android yet... but year agoon the SP3 touch didn't work in Clover with El Capitan hackintosh.

I hope this helps! Good luck!

torstai 29. joulukuuta 2016 19.14.18 UTC+2 Jan Cervenka kirjoitti:

Hi

My issue is probably 1) like you said. It is installed on a parition the Surface Pro 3 sata ssd disk. The partition is formatted to EXT4. When the installer is complete and I select boot now it does boot in. As soon as I reboot I can get it to boot again. Booting live CD works just fine. Are these Files - private any help? I am not sure I got the logcat / dmesg right. If not please tell me how to retrieve them and I will do that.

Thanks for your help! 

On Thursday, 29 December 2016 00:29:02 UTC, Mauro Rossi wrote:

Il giorno mercoledì 28 dicembre 2016 22:07:32 UTC+1, Jan Cervenka ha scritto:

Hi - I am having problems booting your nougat 7.1 builds with 4.9 kernel.

Can you help?

Thanks

Hi Jan, me too...

I know about the following issues (all kernel-4.4 vd kernel-4.9 independent):

1) installing on (S)ATA hard disk is somehow problematic and leads to a non repeateable boot, while booting LiveCD is usually working (but is one-shot)

2) radeonsi is booting, with a modified version of LLVM 3.8.0 "plus AMDGPU target", but  I cannot complete the sign-in (the problem seems related to EGLterminate causing a systematic SIGSEGV MAPERR)

3) latest mesa-dev EGLswapBufferWithDamage patches had to be reverted because it prevents AssetAtlas loading

It seams also that reverting those patches like done in https://github.com/maurossi/mesa - private prevents some nouveau freezes

[Jan Cervenka]

What you suggested works fine, thanks. However I use grub2win. 

Is it possible to edit initrd ? On mySP3 I have to reduce the mic boost value or else I can't use it.. Can you?

Thanks.

[Evan Langlois]

There is nothing stopping you from modifying the img files.  Just boot Linux and mount the img files the same way you would mount a partition.

[Hypo Turtle]

Not for the initrd.img it's a .cpio.gz so unpack it like a zip then as a cpio

[Evan Langlois]

He said changing system.img and rooting.   You normally won't need to modify initrd.img for that.   Also, the ramdisk.img is also in cpio format.  If you use gnu tools (likely), you will want to use "-H newc" when running cpio to make sure its in the official Android format.  The default cpio format won't work.

On Dec 31, 2016, Hypo Turtle <hypot...@gmail.com> wrote:

Not for the initrd.img it's a .cpio.gz so unpack it like a zip then as a cpio

-- Sent with K-@ Mail - the evolution of emailing.

[Mauro Rossi]

Il giorno giovedì 29 dicembre 2016 22:38:48 UTC+1, Wesley Henrique ha scritto:

Wtf Androi-x86 7.1.1 RC0 very stable.

Hi Wesley, all,

I took the chance to try the RC0 for Surface3 iso with HDD installation EXT4 partition

and that one is also affected by the problems I mentioned:

1) (S)ATA install issue: after a Google Play Store update (which is somehow inevitable when sign-in has been perfomed) the systems starts to behave like any process cannot do basic things like opening a SQLlite database of apps

or write in the /data/ folder, thus the system becomes inusable

2) the DEBUG mode is also somehow problematic, even if the 7.1.1 whitelist did not yet came in, 

by not having SElinux domains defined for  serveral items, but I think this may be related again to chroot mechanism used in DEBUG mode (while in a former post I've seen that switchroot is used in non DEBUG mode)

If people with S3 and people using the system.img as a partition are not affected by 1) 

then this may be a clue to a problem specific to EXT4 or to a change performed by Google Play Store at the update

Issue 2) is also impacting the use of DEBUG mode and I don't like very much my workaround of disabling the security features of closing Fds and reopening at fork.

I would suggest to have a look at these two issues, because they are two show stoppers.

Mauro

[Hypo Turtle]

Sorry thought you were replying to Jan

[Jan Cervenka]

Hi - I managed to extract the IMG edit the file I needed and repack. The system boots but UI is very slow and choppy. Have you experienced this? Or can you tell me how I can root it and then edit the file when im booted in ?

[Andreas Voigt]

Hi Mauro,
i have installed your 32bit iso with kernel 4.9 so far everthing is fine.
but
youtube or netflix doesn't work...
dmesg shows "E Drm : Failed to find drm plugin"

any suggestions and is there any option to get widevine into this image?

Thanks

[Andreas Voigt]

Am Mittwoch, 28. Dezember 2016 01:14:46 UTC+1 schrieb Mauro Rossi:

On youtube i get

E Drm : Failed to find drm plugin

any suggestions and is the a solution for widevine

[youling 257]

https://osdn.net/projects/android-x86/scm/git/frameworks-base/commits/cc8c13896a8f6b65664a4ee191fcc2b850b9ddef  ，whitelist 

在 2016年12月28日星期三 UTC+8上午8:14:46，Mauro Rossi写道：

[Xuefer H]

I have drm hwcomposer working for android x86_64 cm-14.1. any chance and how to push?

it requires merging some aosp to multiple repos in order to match cm version

[youling 257]

"/android/", 9)) only can make Android 6.0.1 release 74(November security patches) work on debug mode 

在 2017年1月11日星期三 UTC+8下午9:24:18，youling 257写道：

[youling 257]

0001-DO-NOT-MERGE-temporary-workaround-for-Fds-whitelist-.patch can make android-6.0.1_r77 and android-7.1.1_r13 work on debug mode . 

@Chih-Wei Huang

在 2017年1月12日星期四 UTC+8上午4:32:44，youling 257写道：

[Chih-Wei Huang]

2017-01-12 3:15 GMT+08:00 Xuefer H <xue...@gmail.com>:
> I have drm hwcomposer working for android x86_64 cm-14.1. any chance and how
> to push?

You can put it to a git repo and give me
a pull request.
Or just send the necessary patches to the list.
Thank you!

> it requires merging some aosp to multiple repos in order to match cm version

Will update that later.



--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Wesley Henrique]

Thanks, not has support for graphic card Intel GMA X4500, not started, black screen command line. :(