[Beta] [11] ProjectSakura-x86 for PC's [OFFICIAL]

Search This thread

Lisbet111111

Member
Jul 12, 2022
12
0
good, so it does work, the 2nd one is for AMD/virtio-gpu so not working is correct
Got it, thank you. And btw, one more question, which branch is the correct branch for ProjectSakura-5.2-OpenGapps-pico-20220428-1532--OFFICIAL.iso(2022-04-29)?

Follow https://github.com/supremegamers/android/tree/sakura/11-x86,
I synced sakura/11-x86 branch and built locally, but met some build error,
1) zstd not found // fixed. use gzip instead
2) meson not found // fixed. pip3 install meson, and add ~/.local/bin to PATH
3) finalizeWorkProfileProvisioning not found // fixed. just comment out, since this method not found in framework side
4) out of a total partition size of 3524313088 bytes (3361 MB) // fixed. increase system partition size
5) use rufus-3.19 to install, failed to install, refer to attached file, reboot again and again

Build command:
. build/envsetup.sh && lunch android_x86_64-userdebug && export USE_FOSS_APPS=true && make -j8 iso_img
 

Attachments

  • failed_to_install.jpg
    failed_to_install.jpg
    1.4 MB · Views: 34
  • kernel_panic.jpg
    kernel_panic.jpg
    265 KB · Views: 36
Last edited:
Got it, thank you. And btw, one more question, which branch is the correct branch for ProjectSakura-5.2-OpenGapps-pico-20220428-1532--OFFICIAL.iso(2022-04-29)?

Follow https://github.com/supremegamers/android/tree/sakura/11-x86,
I synced sakura/11-x86 branch and built locally, but met some build error,
1) zstd not found // fixed. use gzip instead
2) meson not found // fixed. pip3 install meson, and add ~/.local/bin to PATH
3) finalizeWorkProfileProvisioning not found // fixed. just comment out, since this method not found in framework side
4) out of a total partition size of 3524313088 bytes (3361 MB) // fixed. increase system partition size
5) use rufus-3.19 to install, failed to install, refer to attached file, reboot again and again

Build command:
. build/envsetup.sh && lunch android_x86_64-userdebug && export USE_FOSS_APPS=true && make -j8 iso_img
I haven't touched the project for a while and moving to other ROMs, so I haven't put new fixes yet. But if you want I'll remember what I did.

1. If zstd is not found, install it on your Linux distro, I think you'll know how (`sudo apt install zstd` or something)
2. Use meson that the distro providie
5. I haven't worked on the iso and the install.img yet so iso install is broken currently.
 

Lisbet111111

Member
Jul 12, 2022
12
0
I haven't touched the project for a while and moving to other ROMs, so I haven't put new fixes yet. But if you want I'll remember what I did.

1. If zstd is not found, install it on your Linux distro, I think you'll know how (`sudo apt install zstd` or something)
2. Use meson that the distro providie
5. I haven't worked on the iso and the install.img yet so iso install is broken currently.
Thanks a lot, already apt install zstd, but still met the iso install issue.
When Making iso image, there's below error message,
isohybrid: Warning: more than 1024 cylinders: 1376
isohybrid: Not all BIOSes will be able to boot this device

but within the same build environment, for blissos, there's NO such error message, and iso install is ok to boot.
I doubt that iso install is related with this error message, but don't know how to fix:cry:
Have you ever met such error message? hope to get some comments..
 
Last edited:
Thanks a lot, already apt install zstd, but still met the iso install issue.
When Making iso image, there's below error message,
isohybrid: Warning: more than 1024 cylinders: 1376
isohybrid: Not all BIOSes will be able to boot this device

but within the same build environment, for blissos, there's such error message, and iso install is ok to boot.
I doubt that iso install is related with this error message, but don't know how to fix:cry:
Have you ever met such error message? hope to get some comments..

I haven't got the message because I know what is going on, now I have to work on both install.img and initrd.img to update the components inside it.
 

Lisbet111111

Member
Jul 12, 2022
12
0
I haven't got the message because I know what is going on, now I have to work on both install.img and initrd.img to update the components inside it.
Hello Sir, sorry for trouble again and again, thank you very much, refer to sakura code base, I've porting several git, drm_hwcomposer, mesa, llvm, libdrm, etc,
after that, dual monitors have been supported on blissos 14 + porting, thanks again.
 
Last edited:

dweiks

Member
Feb 3, 2016
13
0
Guys we need a better tutorial to how to install the OS. I don't understand anything. Its not working
 

kamazok

Member
Aug 22, 2015
46
13
Guys we need a better tutorial to how to install the OS. I don't understand anything. Its not working
I assume that you just have an old processor without support for SSE4.2 instructions, or a video card from Nvidia. I would advise you to roll back to Android 9 (TV) x86 or Prime OS Classic (on Android 7). These assemblies are the best for older computers.
 

waheem

Senior Member
Dec 10, 2014
487
87
It's been a while since the last update, but well whatever I got some new builds here with lots and lots of changes :D.
This is not only a big release but a special one, currently I am typing this reply on 10:55PM, more than an hour later gonna be Lunar New Year, yay 🥳🥳🥳

So let's see what do we have :
- Merge latest January patch
- Bromite SystemWebview updated to 96.0.4664.54
- Implement a DPI fix by PrimeOS Team (big thanks to them)
- Update alsa-lib/alsa-utils/alsa-ucm-conf to 1.2.6.3
- firmware now getting all the latest from linux-firmware, including some silead linux firmware from gsl-firmware repo
- Replace rusty-magisk with Project Kokoro, a new way to implement Magisk into Android-x86 build with Zygisk and modules support (a big thanks to @huskydg for helping me with this), also everything relate to koushSU is removed.
- Added input wiring to AUDIO_DEVICE_IN_WIRED_HEADSET, hoping that it can help detect mics better.
- NTFS can now being mounted as SDCard (default is using ntfs-3g + fuse, there's also Paragon's ntfs3)
- ntfs-3g merged to latest commit
FJZv9N2aQAU1akg

- libhoudini now change from ChromeOS one to WSA, which increase compability as some people report.
- Update Mesa3d to 23.1.4 with LLVM13 + libdrm 2.4.109
+ For Intel, i965 driver is being default instead of crocus and iris to prevent glitches and crashes
+ You can now use drirc, a drirc file is in /system/etc, you can add your config folder at /data/drirc.d/ and add your own *.conf file in
- drm_gralloc now completely removed (goodbye)
- gbm_gralloc change to the branch that BlissOS 15 use
- minigbm change to maurossi's gbm_mesa_y22_w02_R which is the version with gbm_backend to use minigbm with gbm_backend, read down below
- hw_composer updated
- Import some sepolicy from Project Celadon, this include graphics/mesa, thermal and houdini
- Kernel is now updated to 5.15.16 with lots of improvement. (more on this soon)
- system.sfs, initrd.img and install.img now compressed with zstd.

There could be more changes, hopefully I can find all of them.....

Now to use minigbm there'll be 4 options :
+ minigbm,
+ minigbm_gbm_mesa (the one with gbm_backend),
+ minigbm_intel (for Intel iGPUs only)
+ minigbm_arcvm (the code suggest this thing is for virtio-gpu)
I only tested minigbm_gbm_mesa and minigbm_intel so far and it can boot. If you want to try this gralloc then add this into the 2nd line of the grub code (aka your cmdline)

GRALLOC=minigbm_gbm_mesa HWC=drm_minigbm

Also, the build implement some properties that was a part of Phoenix OS Darkmatter, I add them here, all of them are used to change Mesa3d environment variables, including :
mesa.gles.override - MESA_GLES_VERSION_OVERRIDE : override GLES version
mesa.loader.override - MESA_LOADER_DRIVER_OVERRIDE : override Mesa loader driver (like i965 to iris or crocus)
mesa.galliumhud.value - GALLIUM_HUD
mesa.galliumhud.period - GALLIUM_HUD_PERIOD
These are the variables for GalliumHUD, the HUD to show FPS, CPU,etc on Gallium3D driver, you can read more in this page to set up


Finally, as the build now go OFFICIAL state, I'll upload them in Project Sakura SourceForge instead of blissos-dev one.

Enjoy the build :), and thanks for your support.
Happy Lunar New Year to everyone 🐧
Can you provide list of wifi and bt module hardware model number that including this kernel or how to check of witch hardware added in this kernel
 
Can you provide list of wifi and bt module hardware model number that including this kernel or how to check of witch hardware added in this kernel
It's hard to do that though because I don't have every single wifi card out there to check, so I'm not interested in this.
However, if you have a problem with wifi card then I guess you can have a feedback
 
  • Like
Reactions: gfsLuc

waheem

Senior Member
Dec 10, 2014
487
87
It's hard to do that though because I don't have every single wifi card out there to check, so I'm not interested in this.
However, if you have a problem with wifi card then I guess you can have a feedback
It's hard to do that though because I don't have every single wifi card out there to check, so I'm not interested in this.
However, if you have a problem with wifi card then I guess you can have a feedback
 

waheem

Senior Member
Dec 10, 2014
487
87
I have a rtl8188eu wifi adapter when I flashed xanmod][GoogleLTS][codenam pledge] Kernel 5.10.58 for Android-x86 wifi did not work so i dicide to flashed xanmod][zen-kernel][GoogleLTS][codename:benares] Kernel 4.19.x for Android-x86 4.19.203 and my wifi working perfectly so my query what to do with pledge kernel to work my rtl8188eu
 

waheem

Senior Member
Dec 10, 2014
487
87
wait a sec
1. How can you put Gearlock on PS-x86 ?
2. The kernel in here already have rtl8188eu support, why do you have to downgrade ?
Running old android version maybe android 9 pubg edition rom x86 both kernel working on this rom https://mega.nz/file/G1VDBIYa#plF2ObX_8NhPJtJXz81aJOBzKj5ev3MsV3_HSKE2RzA but but with benares kernel wifi working and pledge kernel wifi didn't work
Does pledge kernel have rtl8188eu
And yes suggest me one of suported bt adapter then I order a new one
 

waheem

Senior Member
Dec 10, 2014
487
87
Manually install gearlock some kinds of comands pc
Running old android version maybe android 9 pubg edition rom x86 both kernel working on this rom https://mega.nz/file/G1VDBIYa#plF2ObX_8NhPJtJXz81aJOBzKj5ev3MsV3_HSKE2RzA but but with benares kernel wifi working and pledge kernel wifi didn't work
Does pledge kernel have rtl8188eu
And yes suggest me one of suported bt adapter then I order a new one
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    header.png


    Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.

    This is an unofficial port of Project Sakura for PCs running x86 CPUs by using patches provided by Android-Generic project.

    Yep1l4L.png

    Made with Android-Generic v2.0 - Android for PCs & GSI devices
    More detail : https://android-generic.github.io/

    disclaimer.png


    Code:
    * Your warranty is now..... I don't know this is PCs ¯\_(ツ)_/¯
    * It's very important to read the instructions and understand what you are doing. So please, READ !
    * I am not responsible if you accidentally wiped your data on your hard drives or making your main OS like Windows unable to boot.
    * You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.


    "This is a user friendly thread, all your suggestions are important to us and will be taken into consideration."



    flashing.png

    Currently the best method I recommend to use is to dual-boot with a Linux distro, using its Grub2 bootloader to load the OS.You can check out BlissOS wiki or SupremeGamers wiki for the instruction.


    Alternatively, If you want to install using Windows

    For .rpm

    I DON'T RECOMMEND TO FLASH ISO ON USB BECAUSE THE BOOTABLE INSTALLER IS HAVING PROBLEM.

    download.png

    Click Here



    credits.png


    -Android-x86 Project

    -BlissLabs (with works like BlissOS and Android-Generic)

    -Lineage OS

    -AOSP

    -Superior OS

    -AOSiP

    -DerpFest

    -Pixel Experience

    -Extended UI

    -Havoc OS

    -CrDroid ROM


    source.png



    Project Sakura Source
    The kernel source which I use for the build : https://github.com/hmtheboy154/Darkmatter-kernel

    ProjectSakura-x86 Source which include all the changes for x86 will be available soon
    ProjectSakura-x86 source : https://github.com/supremegamers/android/tree/sakura/11-x86/

    support.png


    Project Sakura's Telegram Group (if you want to feedback about the ROM)

    BlissOS/ AG (x86/ x86_64) Telegram Group (if you need help installing or feedback about the PC builds)


    miscinfo.png

    This is a x86_64 build so please make sure your CPU support 64bit and SSE4.2

    About bugs : Unlike Custom ROMs on phones where people can just put "You tell me", PC builds do have problem..... a lot.
    - Not all the hardware will work perfectly or even supported (*cough Nvidia GPUs ).
    - Screen Recording is not working yet (gbm_gralloc limitation)
    - FaceUnlock is not working (and don't even hope it work)
    - Bluetooth might not working yet.
    - SwiftShader is broken so you can't boot with Software Rendering.
    - For user using AMD GPUs (or APUs), there's graphic bugs when you have to choose default apps like for default launcher or default browser. Here's an explanation by Mauro Rossi - one of the member of Android-x86 Project :

    A long standing issue is "the tiling artifacts" happening with gbm_gralloc at ResoverActivity window when SW write buffer used, one example is the launcher selector at first boot and another is visible with Chicken Invaders advertisements windows on SW write buffer


    Intel i915 and i965 were not affected, while r300, r600, radeonsi and nouveau are all affected,

    iris and crocus expected to not be affected, but I need to check.

    So if you are seeing this (or worse) then it's the one I'm talking about.

    (Iris and crocus actually not affected btw)
    Update : Iris got reported to be affected, and there are some cases of crocus too. So I will mark this as a bug for both AMDGPUs and Intel iGPUs in general. If you want to read more about the bug, you can read this post by Mauro for more info

    bug.jpg


    Project Sakura-x86 for PCs
    Maintainer: HMTheBoy154
    Build Type: Unofficial

    ROM OS Version:
    11.0 r40
    ROM Kernel: Linux 5.10.61
    ROM Firmware Required: Included in the build
    Based On:
    LineageOS 18.1

    Version Information
    Status: Alpha
    Current Stable Version:
    5.R
    SELinux Status : Permissive
    Release Date:
    2021-09-06
    4
    It's been a while since the last update, but well whatever I got some new builds here with lots and lots of changes :D.
    This is not only a big release but a special one, currently I am typing this reply on 10:55PM, more than an hour later gonna be Lunar New Year, yay 🥳🥳🥳

    So let's see what do we have :
    - Merge latest January patch
    - Bromite SystemWebview updated to 96.0.4664.54
    - Implement a DPI fix by PrimeOS Team (big thanks to them)
    - Update alsa-lib/alsa-utils/alsa-ucm-conf to 1.2.6.3
    - firmware now getting all the latest from linux-firmware, including some silead linux firmware from gsl-firmware repo
    - Replace rusty-magisk with Project Kokoro, a new way to implement Magisk into Android-x86 build with Zygisk and modules support (a big thanks to @huskydg for helping me with this), also everything relate to koushSU is removed.
    - Added input wiring to AUDIO_DEVICE_IN_WIRED_HEADSET, hoping that it can help detect mics better.
    - NTFS can now being mounted as SDCard (default is using ntfs-3g + fuse, there's also Paragon's ntfs3)
    - ntfs-3g merged to latest commit
    FJZv9N2aQAU1akg

    - libhoudini now change from ChromeOS one to WSA, which increase compability as some people report.
    - Update Mesa3d to 23.1.4 with LLVM13 + libdrm 2.4.109
    + For Intel, i965 driver is being default instead of crocus and iris to prevent glitches and crashes
    + You can now use drirc, a drirc file is in /system/etc, you can add your config folder at /data/drirc.d/ and add your own *.conf file in
    - drm_gralloc now completely removed (goodbye)
    - gbm_gralloc change to the branch that BlissOS 15 use
    - minigbm change to maurossi's gbm_mesa_y22_w02_R which is the version with gbm_backend to use minigbm with gbm_backend, read down below
    - hw_composer updated
    - Import some sepolicy from Project Celadon, this include graphics/mesa, thermal and houdini
    - Kernel is now updated to 5.15.16 with lots of improvement. (more on this soon)
    - system.sfs, initrd.img and install.img now compressed with zstd.

    There could be more changes, hopefully I can find all of them.....

    Now to use minigbm there'll be 4 options :
    + minigbm,
    + minigbm_gbm_mesa (the one with gbm_backend),
    + minigbm_intel (for Intel iGPUs only)
    + minigbm_arcvm (the code suggest this thing is for virtio-gpu)
    I only tested minigbm_gbm_mesa and minigbm_intel so far and it can boot. If you want to try this gralloc then add this into the 2nd line of the grub code (aka your cmdline)

    GRALLOC=minigbm_gbm_mesa HWC=drm_minigbm

    Also, the build implement some properties that was a part of Phoenix OS Darkmatter, I add them here, all of them are used to change Mesa3d environment variables, including :
    mesa.gles.override - MESA_GLES_VERSION_OVERRIDE : override GLES version
    mesa.loader.override - MESA_LOADER_DRIVER_OVERRIDE : override Mesa loader driver (like i965 to iris or crocus)
    mesa.galliumhud.value - GALLIUM_HUD
    mesa.galliumhud.period - GALLIUM_HUD_PERIOD
    These are the variables for GalliumHUD, the HUD to show FPS, CPU,etc on Gallium3D driver, you can read more in this page to set up


    Finally, as the build now go OFFICIAL state, I'll upload them in Project Sakura SourceForge instead of blissos-dev one.

    Enjoy the build :), and thanks for your support.
    Happy Lunar New Year to everyone 🐧
    3
    This is the first initial build which include FOSS pack from BlissOS. FOSS pack provide some FOSS application and also microG as the GMS replacement. Also here's what I put into the build :
    - Mesa 21.2.1, libdrm 2.4.107 and LLVM12.0.1
    - alsa-utils and alsa-lib are on version 1.2.5.1 with alsamixer tool
    - My customized Kernel 5.10.61 which include patches from GoogleLTS (kernel/common android13-5.10 branch), xanmod and Android-x86 (More detail)
    - AOSP SystemWebView got replaced with Bromite SystemWebView (big thanks to them for providing x86_64 builds)
    - Using FakeStore 0.1.0 instead of 0.0.2 provided by FOSS package.
    - Adding Open Camera since the stock Camera app is broken.

    Here are some screenshot :
    3
    It's almost May which mean summer is coming and before May I want to release new builds of PS-x86. Unfortunately If you don't know Project Sakura is officially deprecated, meaning that the ROM is dead so this will be the last build of ProjectSakura-x86. This seems to be a bad news however I will officially working on BlissOS too so If you want another Android-x86 build running Android 11 made by me you can check out some BlissOS 14.x builds in the future (and some other Android version too). I'll also planned to move on from PS to another ROM and help them making x86 version for both 11 and 12L build of it.

    But anyway, I still hope that you can enjoy this one last build of PS-x86, here are the new changes :
    - Merge March patch.
    - Go back to AOSP Webview, however for those who want to use Bromite Webview, PS-x86 already add Bromite WV to the webview list so If you want you can use them.
    - Upstream the kernel to 5.15.35, ofc this time there will be no kernel panic
    - There will be another new method of embedding Magisk into the build in Kokoro without the pain of touching the system, this time based on the initrd-magisk to implement Magisk into initrd (Again, huge thanks to @huskydg for helping me).
    - Mesa updated to 21.3.8.
    - drm_hwcomposer updated to latest commit.
    - For minigbm, currently minigbm_gbm_mesa is broken due to rebasing with latest branch. However, minigbm can now work with AMDGPUs. Yea that's right, thanks to my friend @Ni8 at SupremeGamers forum tested it out. So now minigbm_intel can be used on Intel iGPUs and minigbm can be used on AMD GPUs/APUs.
    There's also a change that minigbm or minigbm_arcvm can work with virtio-gpu too for those people who want to run it on VM but don't like gbm_gralloc.
    - Lawnchair got replaced with Lineage's Trebuchet for those who want to use the Desktop Mode on external display.
    - FOSS builds now follow a new apps list, which includes :
    • Aurora App Store - com.aurora.store
    • Aurora Fdroid - com.aurora.adroid
    • Calendar/Contacts sync - com.etesync.syncadapter
    • LocalGsmNlpBackend - org.fitchfamily.android.gsmlocation
    • microG and all the dependencies
    - Termux, Open Camera and Taskbar got updated.
    - Include a new storage fix where apps can't be able to read Android/data or Android/obb inside /sdcard due to the new permissions issue in 11. This fix is actually made by PrimeOS again by granting 777 whenever an app open. It could be a temporary fix should not be used in long-term and instead we should find a way to bind-mount data and obb using some kind of special filesystems.
    But that's will be a whole new journey, right now I wanna give them a big thank you for helping us by providing the fix.
    - Data Usage - a feature of Project Sakura ROM will be disabled as a default due to the fact that it made SystemUI crashing. Not to mention we can't be able to use SIM cards yet so it's useless anyway

    There could be more changes that I don't remember. But here's the download link as usual and...... have fun :D.
    2
    For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
    Open termux, type following commands.
    Bash:
    su
    nano /default.prop
    Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
    alternatively,
    Bash:
    su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'