This is my Rom № 46 (Android 10) .
Working(should working):
Phone calls
SMS
Camera
Bluetooth works there!
WIFI
GPS
Location services
SDcard as internal storage
LiveDisplay
Voltage control.
These things are NOT working (don't ask!)
Encryption (haven't tested it)
FM-Radio (not included)
NFC-HCE
LED for charding battery
SELinux is set permessive.
How to install:
1) use TWRP 3.5.0.
2) wipe system, data, cashe, dalvik;
3) Flash the firmware, magisk and gapps.
Change log:
20220521- initial build.
Last builds are here.
Sources:
https://github.com/crdroidandroid
https://github.com/Alex009988/android_kernel_sony_msm8994
alex009988 said:
Sources:
https://github.com/crdroidandroid
https://github.com/sabarop/android_kernel_sony_msm8994
https://github.com/sabarop/android_device_sony_karin
https://github.com/sabarop/android_device_sony_karin_windy
https://github.com/DevelLevel/android_device_sony_kitakami-common
https://github.com/Professor-Berni/android_device_sony_kitakami-common
https://github.com/Professor-Berni/android_device_sony_suzuran
Click to expand...
Click to collapse
Thanks for the share
I've noticed on this and other karin threads you list either multiple kernels or multiple common libraries (android_device_sony_kitakami-common), with in this case another device altogether (suzuran)
Out of curiosity, why is that?
Presumably you quote the actual sources used for the build and the others are additional resources?
alex009988 said:
Sources:
https://github.com/BootleggersROM
https://github.com/DevelLevel/android_kernel_sony_msm8994
https://github.com/sabarop/android_kernel_sony_msm8994
https://github.com/sabarop/android_device_sony_karin
https://github.com/sabarop/android_device_sony_karin_windy
https://github.com/DevelLevel/android_device_sony_kitakami-common
https://github.com/Professor-Berni/android_device_sony_kitakami-common
https://github.com/Professor-Berni/android_device_sony_suzuran
Click to expand...
Click to collapse
Here, two kernels, two kitakami-common sources and suzuran device again ... :-?
scoobydu said:
I've noticed on this and other karin threads you list either multiple kernels or multiple common libraries
Click to expand...
Click to collapse
That means that I used sabar tree but used some commits from berni. So for kernel I used berni kernel but took livedisplay fix commits from sabar.
alex009988 said:
That means that I used sabar tree but used some commits from berni. So for kernel I used berni kernel but took livedisplay fix commits from sabar.
Click to expand...
Click to collapse
So none of them are your final sources, that were used to build the images, but rather the snippets and collections of the various sources making them up.
scoobydu said:
So none of them are your final sources, that were used to build the images, but rather the snippets and collections of the various sources making them up.
Click to expand...
Click to collapse
I can publish the final device,kernel,vendor to the cloud if anyone is interested in building a rom too. It will be good if anybody would be making roms too for our tablet.
alex009988 said:
I can publish the final device,kernel,vendor to the cloud if anyone is interested in building a rom too. It will be good if anybody would be making roms too for our tablet.
Click to expand...
Click to collapse
Edit, after many months you either don't know how, or have no intention of sharing the actual sources used to build the rom.
<Moderator Note>
Closed thread. @alex009988 please see my PM and use the Report button on the OP to let us know if you're prepared to fix the thread, so we can unlock it.
Thank you,
@roirraW "edor" ehT
roirraW edor ehT said:
<Moderator Note>
Closed thread. @alex009988 please see my PM and use the Report button on the OP to let us know if you're prepared to fix the thread, so we can unlock it.
Thank you,
@roirraW "edor" ehT
Click to expand...
Click to collapse
@alex009988 I've reopend your thread to allow you to publish a link to the correct kernel source i.e. to YOUR kernel source. For more information refer to my PM.
Regards
Oswald Boelcke
Senior Moderator
Oswald Boelcke said:
@alex009988 I've reopend your thread to allow you to publish a link to the correct kernel source i.e. to YOUR kernel source. For more information refer to my PM.
Regards
Oswald Boelcke
Senior Moderator
Click to expand...
Click to collapse
Thank you for this opportunity. I've done it. I'll correct link in my other roms too soon enough.
Related
hi all
in this Topic i am making android 4.0.4
Part of the ROM files tigrouzen
DOWNLOADS
ROM
MOD EDIT: Link removed.
kernel
nand
MOD EDIT: Link removed.
sd
soon ...
patches
wifi &bt wave 2
MOD EDIT: Link removed.
gapps for this rom
http://www.mediafire.com/download/zfe72bjtnsjt787/google_for_nimaics.zip
features
. ROM: 66mg
. stable
. very smooth and fast
. Excellent battery
. odexed rom
. add file & code for Optimization
. zipaling
. Base rom: slim
. change or deleted app
. Enhanced sound quality
. Space, RAM: 160mg
. other ...
Installation
Bada 2.0 is required
copy rom.zip &kernel (zImage) to memory
flashed boot & fota
for s8500
MOD EDIT: Link removed.
for s8530
MOD EDIT: Link removed.
Reboot the phone holding Power and home
CWM Recovery starts, pick:
go to
install zip/choose zip from from storage/sdcard/rom name.zip/yes
after installed reboot and startup android
THANKS TO
thanks for files & kernel [tigrouzen]
volk204
Rebellos
blue59
alberto96
and other Badadroid devs
reserved
Kernel sources?
volk204 said:
Kernel sources?
Click to expand...
Click to collapse
kernel for tigrouzen (iczenrom)
i just make rom
nima.yavari said:
kernel for tigrouzen (iczenrom)
i just make rom
Click to expand...
Click to collapse
no kernel sources - no ROM here
volk204 said:
no kernel sources - no ROM here
Click to expand...
Click to collapse
why?
So what do I do?
nima.yavari said:
why?
So what do I do?
Click to expand...
Click to collapse
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
volk204 said:
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
Click to expand...
Click to collapse
ok
i can't put just rom?
no kernel to this topic
You are still don't know, Why Tigrouzen isn't here
thnks
cfernr said:
how to perform nand install?
Click to expand...
Click to collapse
read post 1 Installation
nima.yavari said:
read post 1 Installation
Click to expand...
Click to collapse
why not nand 4.4.3?
cfernr said:
why not nand 4.4.3?
Click to expand...
Click to collapse
kernel tigrouzen erorr fc com.phone
need new kernel for 4.4.3
Awesome work bro!
Keep up the good work and make even more ROMs.
is GPS working on this rom?
cfernr said:
is GPS working on this rom?
Click to expand...
Click to collapse
yes
nima.yavari said:
yes
Click to expand...
Click to collapse
i cant have gps working? any app or something to fix it?
imho this is the best rom ever for the wave
The GPLv2 requires you to share the source code if you've modified anything in the kernel. This is not optional, you are obliged to do so. Non GPL compliant works simply do not belong on XDA (please report any you encounter).
OP, you may PM me once you're ready to upload the full, working sources.
You can review the forum rules here and read more about the GPL here and here. Thread closed.
This info is intended to go for all developers that want to start/continue development on Android 6.0 and up, but every user can contribute to this discussion too.
The main purpose of the discussion is to find the root cause of our issues due to the new patches upstream.
Click to expand...
Click to collapse
Please rate and comment, so this can be on top of the Discussion Forum, since this is vital for future development.
Click to expand...
Click to collapse
Basic introduction:
From November 09th of 2016 and up Android is trying to patch the framework sources with file descriptor testing (fd), which is causing the mentioned bootloops across our platforms.
More about what FDs are can be found here --> https://en.wikipedia.org/wiki/File_descriptor
Specifically I have seen issues arising to Samsung devices, since that OEM always makes its own workarounds on libraries and framework, without supporting AOSP.
Conflicting commit:
https://github.com/CyanogenMod/android_frameworks_base/commit/b8be33b0bedec211708c4525b9d3f3b4effb385c
Click to expand...
Click to collapse
ROM expected behaviour:
FDs should be recognized and closed properly.
Click to expand...
Click to collapse
ROM behaviour after patch:
An unknown FD stays open (fd==5), and causes the ROM to be stuck into a bootloop, due to Zygote crashing.
Click to expand...
Click to collapse
A workaround has been made know as FD Whitelisting Procedure.
FD Whitelisting example commit:
https://github.com/CyanogenMod/android_device_asus_msm8916-common/commit/6392867d973715a84b4fa76a191b4d4c6d2e5d14
Click to expand...
Click to collapse
I have reported it to CyanogenMod and they are working on it.
Workarounds by CyanogenMod: (currently WIP)
https://review.cyanogenmod.org/#/c/174077/3
https://github.com/Bauuuuu/frameworks_base/commit/04fe03b3a6183537eb87c31030822e2e77571945
Click to expand...
Click to collapse
It has been reported by @rovo89 (Xposed developer) also. You can check the GitHub conversation below.
You will find a very good explanation on mostly everything related.
Xposed workaround:
https://github.com/rovo89/XposedBridge/issues/129#issuecomment-261721656
Click to expand...
Click to collapse
Mentioning for help:
@jackeagle
@TheWhisp
@CTXz
@DJ_Steve
(Attached logcat after cherry-picking https://github.com/Bauuuuu/frameworks_base/commit/04fe03b3a6183537eb87c31030822e2e77571945)
Let me know your opinion by commenting below. Thank you for your time.
@Nick Verse Maybe this is useful, look at lines 26 to 32. system_server.te. I know almost nothing of development but give me a couple of words and I'll look for it .
Griasahi said:
@Nick Verse Maybe this is useful, look at lines 26 to 32. system_server.te. I know almost nothing of development but give me a couple of words and I'll look for it .
Click to expand...
Click to collapse
No problem Griasahi! This file is for SELinux policy. (one of the files that tell the OS what to allow, in short, during building)
Thanks for your effort.
Helpful for devs!
Deleted.
Hi
After LeMax2 Project Treble port, I decide to bring up to our device too. Since I've x720 6/64 variant this project was possible to me tho due to QFIL tool in case of bricks, but wasn't need thanks for god.
Project Treble as Work in progress, please read the OP before flash/bla.
and let's the party begin. check sreenshots in "Screenshots" or in the second post.
READ ME FIRST:
it's a buggy rom: I don't care about that, since I put [WIP] that mean new fixes will coming up.
Respect works of devs because they spend time and energy to do these things.
I did not tolerate ETA.
Compatible Devices:
x720: yes.
x722: yes.
x727: yes.
How is possible:
click here.
How I done:
Porting patches of TWRP to our one that I will release one for us too.
Applying the kernel patch from LeMax2 one to mount vendor on ZL1.
Compile the whole rom with Project Treble flags in device tree and proprietary blobs.
Works
Audio.
ADB.
Bluetooth.
Camera.
Display.
Fingerprint.
Graphics: hwcomposer & gralloc.
Internal Storages.
Hardware navigation buttons.
LeEco Extras.
Lights.
NFC.
RIL
Sensors.
USSD Codes: seems works
Wifi.
Bugs
Tell us more, all credits goes to codeworkx fir his fixes and works .
Installation Guide:
Copy my unofficial los to internal storage
Download my own TWRP and flash it via fastboot.
Download the partition.zip from linked thread. credits: @shivatejapeddi
Flash the whole partition.zip (don't panic if give the error it's ordinary administration.)
Go back to Wipe->uncheck all partition except the vendor, tap swipe to wipe it then.
Optional: you can go to Mount to see if mounted.
Wipe: dalvik, cache, data and system.
Now flash the whole rom that will install the vendor.img automatically, reboot device once finish installing then.
Enjoy Project Treble.
TWRP
Click here.
Credits:
LePro3 Developers.
LeMax2 Developers, without them wasn't possible for the unsed partition.
Sources:
https://github.com/hak86
XDA:DevDB Information
Treble x72x, ROM for the LeEco Le Pro3
Contributors
haky 86
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.18.x
ROM Firmware Required: EUI 20s or Newer
Based On: LineageOS
Version Information
Status: Testing
Stable Release Date: 2018-07-25
Beta Release Date: 2018-07-25
Created 2018-07-25
Last Updated 2018-07-24
** Note **
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
** Note **
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
How Can I flash Android P Developer Preview 5:
Click on the following link.
Download ARM64 System A image. and 3 zips for post GSI.
Flash the system.img of Android via fastboot (recommend).
Reboot to TWRP.
Go to Mount-> check Vendor partition.
Flash the 3 zip as they arranged (1-2-3),
Reboot, enjoy Android P DP5.
NOTE:
This project has nothing to do with official updates, I did Project Treble by my initiative that will not affect with official roms. Might someone will reconsider supporting Treble even with official update tho?
Damn Congratulations!
I can't do it today. But, I will definitely try it this weekend. Thanks for sharing these test builds. I am definitely looking forward to checking it out!
Thanks again!
I will go ahead and download it and get started ASAP.
---------- Post added at 08:48 PM ---------- Previous post was at 08:41 PM ----------
haky 86 said:
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
Click to expand...
Click to collapse
I just want to say again, that you are awesome for doing this, I didn't think it was possible with this phone. I am blown away! Nice job!
Hmmm can I shirk off my plans and install this right now? lol!
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
I have a question about Gapps, Magisk and firmware.
I assume Firmware is not an issue since it would still get flashed to the correct partition. With Magisk, I assume that you would prefer that we use 16.7?
What should we use for Gapps? Do you have a specific Gapps in mind?
Wonderful Work~
Its a great! Wonderful work, now wait to fix all bugs now.
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
what should i say , it is great job !!!!!
haky 86 said:
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
Click to expand...
Click to collapse
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Any info about IR support and NFC Smartcard Service?
Most hyped project for now, congratulation. Peoples don't even woke up and already you haven't 2 pages of comments and 15 likes. Congratulation! If everything will be good I'll buy you a beer
Crystal-L said:
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
Click to expand...
Click to collapse
let me fix all those bugs and I can port the rom you want then.
shivatejapeddi said:
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Click to expand...
Click to collapse
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
qqzwc said:
Any info about IR support and NFC Smartcard Service?
Click to expand...
Click to collapse
NFC already fixed just check "Works"
D1stRU3T0R said:
Most hyped project for now, congratulation.... If everything will be good I'll buy you a beer
Click to expand...
Click to collapse
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
xen2001 said:
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
Click to expand...
Click to collapse
) hopefully will work on x722, bcs always there is the problem.
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
Can you answer the question about Gapps?
Is a version of Gapps available for this yet?
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
shivatejapeddi said:
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
Click to expand...
Click to collapse
alright, I also forget to edit the mk files like Android.mk in the proprietary blobs probably that's why buggy.. I'll post new screenshots once got fixed :angel:
Damn, I sell my device.
Thank you for your support.
lazye53 said:
Damn, I sell my device.
Thank you for your support.
Click to expand...
Click to collapse
too late <3
well let's give this a go on x722 and see what happens .. Thanks for the hard work, it's highly appreciated !
Built for fun, will maintain until LOS officially supports?
Also it is BETA, so expect bugs maybe.
I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
Initial Setup for Google is buggy, keep hitting back and retrying works.
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1GIhp9B0rg5Z8lHDz5RIzm-gX4U_XbTHK
Device and Kernel Source:
https://github.com/LineageOS/android_device_oneplus_bacon
https://github.com/KiDwayne/bacon
Contact and Join the group!
https://discord.gg/zB3ubnj
Credits to:
LineageOS Team
@franciscofranco
Join My Discord for discussions!
https://discord.gg/zB3ubnj
Changelog for 07FEB build:
Notification LED works! (Thanks to @dar2q) (might require clean flash to work, do tell)
Updated to Febuary Security!
How stable is LOS16.0 for bacon if this is build straight from source? I saw initial device list in gerrit and still don't see bacon there, maybe it's still too buggy? Can't test it now because I'm away from home
LTMendarynas7 said:
How stable is LOS16.0 for bacon if this is build straight from source? I saw initial device list in gerrit and still don't see bacon there, maybe it's still too buggy? Can't test it now because I'm away from home
Click to expand...
Click to collapse
Other than Setup Wizard being a little buggy God knows why, I use it for Youtube and some work related stuff at home. Pretty fine I guess? I also maintain Oneplus2, I would say Pie is already quite stable.
KiD3991 said:
Other than Setup Wizard being a little buggy God knows why, I use it for Youtube and some work related stuff at home. Pretty fine I guess? I also maintain Oneplus2, I would say Pie is already quite stable.
Click to expand...
Click to collapse
Good to know, still impressed that bacon survived 6 major android versions from kitkat to pie..maybe somebody will support it when Q hits us..who knows. btw ty for shearing unofficial build
Thanks for sharing and all the efforts... Can you please confirm that NFC works on this build (tag reading, GPay, etc.)? aptX support? Ant+ support?
mixmax_dp said:
Thanks for sharing and all the efforts... Can you please confirm that NFC works on this build (tag reading, GPay, etc.)? aptX support? Ant+ support?
Click to expand...
Click to collapse
NFC works. APTx I am not sure as I don't use that. My cheapo bluetooth device doesnt support it themselves.
Great job!
Thanks for the build man, keep up the good work! Just wanted to ask, is SELinux enforcing on this build? Thanks!
I don't want to be that guy but where are the links to the sources you used?
Hey there, thanks for this build! Out of curiosity, did you compile it using TheMuppets' proprietary blobs?
CedArctic said:
Thanks for the build man, keep up the good work! Just wanted to ask, is SELinux enforcing on this build? Thanks!
Click to expand...
Click to collapse
yes it is. As it is basically pure los.
eiwarmer said:
I don't want to be that guy but where are the links to the sources you used?
Click to expand...
Click to collapse
Updated! Thanks for the heads up!
Tomoms said:
Hey there, thanks for this build! Out of curiosity, did you compile it using TheMuppets' proprietary blobs?
Click to expand...
Click to collapse
Yeah, is there something I should know. D:
KiD3991 said:
Yeah, is there something I should know. D:
Click to expand...
Click to collapse
Not at all, don't worry! I'm building LineageOS 16 for the first time today and I've just learnt that, instead of pulling the proprietary files from a pre-existing build running on my phone (as the LineageOS wiki suggests), many use TheMuppets' repos. So I've decided to try, and I asked you because I wanted to know if you used them and faced any issues or not.
Tomoms said:
Not at all, don't worry! I'm building LineageOS 16 for the first time today and I've just learnt that, instead of pulling the proprietary files from a pre-existing build running on my phone (as the LineageOS wiki suggests), many use TheMuppets' repos. So I've decided to try, and I asked you because I wanted to know if you used them and faced any issues or not.
Click to expand...
Click to collapse
The day I knew TheMuppets. Never went back. Hahaha
KiD3991 said:
yes it is. As it is basically pure los.
Click to expand...
Click to collapse
wow.. downloading bro thanks
Does your build LED notification light work or not?
Cuz I also build los 16 from source yesterday, but LED not working..
I started build my personal los16 since January,it never got booted until 20th Jan the maintainer push tons of commit.
Sent from my OnePlus3T using XDA Labs
Goog job @KiD3991,
This is not my daily driver but, so far so smooth, I appreciate the work
Leicxan said:
Does your build LED notification light work or not?
Cuz I also build los 16 from source yesterday, but LED not working..
I started build my personal los16 since January,it never got booted until 20th Jan the maintainer push tons of commit.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
The LED's not working on my personal builds as well, however it works if I boot with permissive SELinux (set via the kernel cmdline) using this zip.
I'm pretty sure the culprit is this commit: https://github.com/LineageOS/androi...mmit/b1a798b50807a6c8b27658eeab323dc6a795f184
Thank you for the build, very solid, good battery life, daily driver material. Led not working, using black theme, however notification is white, setup wizard is buggy as stated, but everything on it is pretty awesome! Thanks again! If you could add screenshot function on to buttons, that would be lovely.
As of now I think SELinux I will let it stay Enforced, unless the LED is requested more. Will start a poll I guess?
THIS WAS A TEMPORARY THREAD BUT NOW THE ORIGINAL ONE IS BACK original URL: HERE
I can't access the Original Android Development section what happened
safety1st said:
I can't access the Original Android Development section what happened
Click to expand...
Click to collapse
XDA guys are updating their forum system, some of unpopular subforums got flattened.
but they told me that everything is still work-in-progress and should be back soon.
tarkzim said:
XDA guys are updating their forum system, some of unpopular subforums got flattened.
but they told me that everything is still work-in-progress and should be back soon.
Click to expand...
Click to collapse
Thanks for the heads up
stupid XDA :/
new build released
2020/06/18
Updated to Android 10.0.0_r37 with June security patches.
Upstream updates and fixes.
Kernel memory management updates, Switched to MEMCG instead of Android LowMemoryKiller.
Fixed reboot timeout problems, now reboot to recovery/bootloader are both working.
SELinux is now Enforcing again.
tarkzim said:
THIS WAS A TEMPORARY THREAD BUT NOW THE ORIGINAL ONE IS BACK original URL: HERE
Click to expand...
Click to collapse
THREAD CLOSED on request of @tarkzim! If interested in this ROM please follow the original thread linked above.
Stay safe and stay healthy!
Regards
Oswald Boelcke