[WIP] [8.1][UNOFFICIAL] PixelExperience 8.1 for hammerhead - Nexus 5 Original Android Development

[WIP] [8.1][UNOFFICIAL] PixelExperience 8.1 for hammerhead - Nexus 5 Original Android Development

IMPORTANT: Read this before installing
A bug in the installer causes installation to fail. Please create the folder /tmp/install/bin in TWRP before flashing!
GApps is NOT included in this build, and installing OpenGApps causes Google apps to crash. Try mindthegapps or another package, and let me know what works.
The device tree and kernel are from LineageOS sources. The device tree for @clamor's repartition can be found here. (If you're interested, I just modified BoardConfig.mk for the patch.)
Features (note, this is a WIP, so most of the Pixel stuff doesn't work):
Google Sans on the launcher
Version compatible with @Clamor's repartition
That's about it.
Downloads:
Downloads will be in my Android File Host folder, under PixelExperience and PixelExperience-clamor (for @Clamor's repartition), and maybe DevDB, if it actually works.
Please leave a review!
XDA:DevDB Information
PixelExperience 8.1 for hammerhead, ROM for the Google Nexus 5
Contributors
yagyaxt1068, jhenrique09 (the creator)
Source Code: https://github.com/PixelExperience
ROM OS Version: 8.x Oreo
Based On: AOSP
Version Information
Status: Testing
Created 2019-02-20
Last Updated 2019-02-19

Installed on my Nexus 5 -
* As already stated, we have to create a folder \tmp\install\bin (every time) before installing.
* installation and booting went smooth without boot loop. (I kinda like the boot animation)
* I found it strange that there is no keyboard come along with this rom, I had to get .apk file and install it manually.
* Through mobile data is turned on, I'm not getting data (for this reason I have to switch back to my old rom)
* Apps started crashing unless permitted manually from settings.
* The below given Gaps worked find for me
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
MindTheGapps-8.1.0-arm-20180808_153837.zip
I wish I could use it for longer.

I have the twrp 3.3.1-1 UA with the memory increase to 1.5gb. I created the tmp / install / bin folder but it always keeps giving me error 7 "no such file or directory".
Do I have to go back to the 1gb distribution? to change twrp? also i have unlimited space using google photos?

Related

[ROM][6.0.1] Android Open Source Project [OMS/Substratum][FINAL]

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Issues and reports
Report issues only if you use the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Installation Instructions
Download ROM
Download Gapps (optional)
Place ROM and Gapps in your SD card or Internal Storage
Reboot into recovery mode
Wipe Dalvik/ART Cache, System, Cache and Data
Flash ROM
Flash Gapps (optional)
Flash SuperSU (optional)
Reboot
Download ROM
AOSP-OMS (final build) : Download, Mirror
MD5: f07003cd34ea84f80eb80d0941a2609f
Gapps
OpenGapps (ARM/Android-6.0). I recommend you choose pico or nano version (Stock version also works, i tested this)
Source
AOSP-OMS on Github
Kernel: APQ8064
Credits
AOSP and CodeAurora Forums
The CyanogenMod Team
AOSPB
SlimROMs
Alberto97 (for his works on F-AOSP lollipop)
srisurya95 and akhilnarang for the AOSP-OMS repos
Chippa_a
STRYDER~007
XDA:DevDB Information
Android Open Source Project [AOSP+OMS], ROM for the Sony Xperia ZL
Contributors
CyberWalkMaN
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2016-11-13
Created 2016-11-15
Last Updated 2016-11-15

Changelog
Nov 13: November security patch (MOB31K)
Helpful information
What is AOSP ?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps.
Anyway to get a working system I added some changes from CodeAurora Forum and CyanogenMod. I added also non-AOSP features for a better user experience ("Clear All" button in Recents) and I'm NOT going to add something other.
Click to expand...
Click to collapse
What is OMS / Substratum ?
Substratum is an application, downloadable from the Play Store, that utilizes all of Sony's Overlay Manager Service (OMS), found on the official AOSP code review. This is similar to Layers in terms of stability and customization as it runs off an upgraded version of the Resource Runtime Overlay system, with the added benefit of running up-to-date Sony code on a customized ROM.
More here : https://plus.google.com/communities/102261717366580091389
Click to expand...
Click to collapse
What is RRO ?
Runtime Resource Overlay (RRO) was contributed by Sony to the Android code base. The RRO framework provides the possibility to modify the look and feel of an application while it is running, without any need to change or recompile the application source code. In short, RRO is a Theme Engine replacement which can do wonders!
More here : http://developer.sonymobile.com/201...ce-overlay-framework-to-android-code-example/
Click to expand...
Click to collapse
Q&A - FAQ
Q : Is root access included into AOSP-OMS ?
A : Yes, SuperSU is included now. If not, you have to add root through a flashable SuperSU zip
> BETA-SuperSU-v2.52.zip is recommended.
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.

Works fine. :good:

Why does Minecraft run from 12 to 17fps? Can samebody help me

Is there any way to disable the clear all recent button? I installed xposed and I prefer the one that comes with GravityBox because it's static

[ROM][UNOFFICIAL] LineageOS 14.1 for Galaxy S4 (GT-I9505)los-legacy

// Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
// Info
It's unnoficial LineageOS14.1 for Galaxy S4 Jfltexx (GT-I9505).
// Info
I strongly recommend to perform a backup of your current rom before installation.
Regarding going from unofficial builds to official - or official to unofficial builds that can be done by as described here:
https://wiki.lineageos.org/signing_b...-or-vice-versa
To migrate from unofficial build to official or official to unofficial:
1. download this script
2. ensure that file has LF (UNIX-style) line endings
3. put it on your phone
4. reboot into recovery
5. make a full backup!
6. go to the folder where script is located
7. run: ./migrate.sh official
8. WARNING! rebooting phone now would end in data corruption!
9. flash the official build now (after flashing official build it is safe to reboot)
10. flash Gapps (and any addons)
11. reboot
Installation Procedure : coming from stock rom
TWRP - Odin flashable (I use Odin 3.12)
Build from xx.xx and Gapps + Magisk Root to external SD
01. I take the battery out now, then battery in again and off into the download mode.
02. flash TWRP with Odin (comes in AP). The hooks at Auto Reboot and F. Reset Time out.
03. disconnect USB cable after flash, battery out and in again.
04. boot into recovery -> Allow Modifications
05 Advanced Wipe: Dalvik/ART Cache, System, Data, Internal Storage, Cache (lasts a while)
06. install -> select lineage image, then add more zips and gapps, Magisk then flash
07. patching system image unconditionally runs through with progress bar
08 Open Gapps are flashed, progress bar runs through
09. when done, tap reboot system, Swipe to install TWRP app (or not, if you don't need it)
10. reboot
11. los 14.1/boots. (quite a while ^^)
12. type through the facility
13. read
// Install
Recommend: Rooted device with custom recovery like (TWRP 3.X.X)
// Info Installation Instruction 14.1
rom+ gapps pico or nano ARM + magisk zip on the sd cards
Installation (Clean Install):
Remove device lock (pattern/PIN/...)
Create Nandroid Backup
Fullwipe in recovery (wipe system, data, cache and dalvik)
Flash ROM
Flash Gapps flash (Android 7.1 and ARM)
Flash Magisk or SuperSU
restart
manual Update:
Create Nandroid Backup
Cache and Dalvik in recovery wipen
Flash ROM
restart
// OTA
https://www.los-legacy.de/jfltexx
14.1 update interval monthly
Download: Open Gapps 7.1
(ARM Pico or Nano)
Download: Magisk for Root
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Downloads: TWRP/Baseband/Bootloader
https://www.androidfilehost.com/?w=files&flid=143393
// Thanks / Credits
Code:
* CM team, Omni team
* XDA developers
* Everyone who has contributed to CM on S4
* syphyr and NucWin for their previous work
* Many thanks to invisiblek
// Info Mitsch79 is currently taking over Benlue work
Code:
[B][U]since some users have already asked me about new features[/U][/B]
Since it is a pure lineageos version
and not as optimized as for example from side.
All I do is to get your mobile phone Up-To-Date
and The errors that I do is release themselves or after every update
[B][U]I hope you understand that I don't make any changes to the version[/U][/B]
// for German
[ROM][LINEAGEOS][CM14.1 UNOFFICIAL][7.1.2][I9505] BY MITSCH79
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 14.1 for Galaxy S4 (GT-I9505)los-legacy, ROM for the Samsung Galaxy S4
Contributors
BenLue, Exodusnick, Mitsch79
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-12-16
Last Updated 2020-04-16

<3 <3 <3

thnx to your rom
are there any bugs? does it work camcorder ?

cmert said:
are there any bugs? does it work camcorder ?
Click to expand...
Click to collapse
Jup,
OTA isnt working
Sometimes CAM is crashing (Cant connect to device) After reboot, its working fine

Looking forward to flashing
Thanks for the new build. One thing i like already is the file size. Nice and small. I like to run lean as possible. I will test it out and see how it rolls.:good:

I'm having trouble accessing the download site, and the link to Mega is invalid.

gugugrp said:
I'm having trouble accessing the download site, and the link to Mega is invalid.
Click to expand...
Click to collapse
Sorry, sync fail :/ Download Links are updated.
Greetings

Can I pm you?

deleted

Thanks - works like a charm

[email protected]
Thank you for the rom is very stable have hitherto no bugs can recognize

Hi I noticed that when I take a screenshot andò I try to open it through the statusbar. The Gallery app gets freeze. Am I the only one that gas this bug?. Thanks

Sasagato said:
Hi I noticed that when I take a screenshot and I try to open it through the statusbar. The Gallery app gets freeze. Am I the only one that gas this bug?. Thanks
Click to expand...
Click to collapse
I'm not currently using ROM, but you can download the latest Build to see if it has already been fixed.
http://cm.s3root.ovh/builds/full/

No it isn't fixed In already on the latest build.

Thanks man!

@BenLue:
Is it possible that you use another mirror for your builds?
This one is very slow:
http://cm.s3root.ovh/builds/full/

provide gapps link here.

http://opengapps.org/
Check this one. I took ARM / 7.1 / nano and everything works fine.

Diese Website ist nicht erreichbar
Die Antwort von cm.s3root.ovh hat zu lange gedauert.
Versuchen Sie Folgendes:
Verbindung prüfen
Proxy und Firewall prüfen
ERR_CONNECTION_TIMED_OUT
This website is not available
The answer from cm.s3root.ovh took too long.
Try the following:
Check connection
Proxy and firewall
ERR_CONNECTION_TIMED_OUT

cm-14.1-20161222-UNOFFICIAL-jfltexx.zip
http://cm.s3root.ovh/builds/full/cm-14.1-20161222-UNOFFICIAL-jfltexx.zip
3,5-7,5 Byte/s - 190 MB von 361 MB
This one is very slow

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project

FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...

Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...

Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy

...

...

Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...

Thanks for all JDCTeam

Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言

Thank you Sir, downloading now

Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?

kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!

So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way

atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...

Very very thankful

Thanks for your hardwork, downloading now.

When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk

Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine

MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

[ROM][OFFICIAL][ginkgo][11] AICP r16.1 for Redmi Note 8 / 8T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (OrangeFox Recovery recommended).
3. Wipe the System, Vendor, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest OrangeFox recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_xiaomi_ginkgoDevice tree source:
https://github.com/AICP/device_xiaomi_ginkgoVendor source:
AICP/proprietary_vendor_xiaomi
Contribute to AICP/proprietary_vendor_xiaomi development by creating an account on GitHub.
github.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
@Adithya R
@madmax7896
Information:
ROM OS Version: 11.x
Kernel: Linux 4.14
ROM Firmware required: Latest Firmware from MIUI 21.4.28 and up
Status: STABLE
Release Date: 05-20-2021
You want to see a "normal" night at the "DEV office", click here!!

May 20, 2021
- Initial Build

May 28, 2021
Changelog:
• Fixed Battery Capacity Values
• Switched to Arrow Tree
• Kernel Upstream for 4.14.234
June 20, 2021
Changelog:
• Initial Official release
• June Security Patch
• Fixed missing APN and Keyboard when booting without gapps
• Updated blobs from MIUI 21.5.27
• Upstreamed SurgeX .237
• Disabled blur by default
August 6, 2021
Changelog :
* Blobs updated from LA.UM.9.11.r1-04500-NICOBAR.0 (CAF)
* Updated blobs from MIUI V12.0.1.0.RCOMIXM
* Upstreamed SurgeX .241
* Enabled IORap prefetching
* Undervolt GPU to reduce heat
* Boost GPU to max for blur
August 20, 2021
Changelog :
* Updated blobs from MIUI V12.0.2.0.RCOMIXM
* Upstreamed SurgeX .242
* Various updates and optimization in kernel
* Removed Widewine hack (R fw is now required)
* Boost I/O during bootup to improve boot speed
* Boost CPU during wake for faster faceunlock
* Increased default f2fs checkpoint interval
* Disabled conservative PL boost
October 15, 2021
Changelog:
* Switched to QuicksilveR kernel
* Fixed wakeup spams
* Updated KCAL preview from MIUI12
* Added 2 KCAL preview
* Disable Notification LED on willow
* Fix mic issues
* Added CABC and HBM support
* More changelog from past weekly builds in support group

Screenshots
https://drive.google.com/drive/folders/1FAkpBX5RaIKjc6KaRxsIaeeoZkN8hs9T?usp=sharing

nice

Why does it come without a keyboard? Can't connect to WiFi or login into Play Store because of that.
The ROM feels pretty snappy tho.
I'm on willow (8T) btw.

I'm on willow.
for me, all works perfect, smooth, fabulous battery life !!!!
After three days of use 40% left with 1h 43 min screen on. All the other room I've tried had a lot more battery drain per hour without any usage.

Hi! Few questions:
Does this ROM pass SafetyNet?
In the guide you suggest OrangeFox as recovery, but for OTA you say TWRP is recommended...so which recovery we should flash?

GattoLesso said:
Hi! Few questions:
Does this ROM pass SafetyNet?
In the guide you suggest OrangeFox as recovery, but for OTA you say TWRP is recommended...so which recovery we should flash?
Click to expand...
Click to collapse
• Pass even without Magisk
• It does support both recovery but I recommend OrangeFox

CSAPawn said:
• Pass even without Magisk
• It does support both recovery but I recommend OrangeFox
Click to expand...
Click to collapse
perro

Hi all , i am on latest at this moment version 31/12/2021 . It seems to me that the sound enhancement does not work as it should. Turning these options on or off will not change the sound quality. For example, the same settings on RedmiNote9S "miatoll" work fine .. and you can clearly hear the difference ..

Hayastan said:
Hi all , i am on latest at this moment version 31/12/2021 . It seems to me that the sound enhancement does not work as it should. Turning these options on or off will not change the sound quality. For example, the same settings on RedmiNote9S "miatoll" work fine .. and you can clearly hear the difference ..
Click to expand...
Click to collapse
Sound enchantment do you mean the Xiaomi Parts one?

CSAPawn said:
Sound enchantment do you mean the Xiaomi Parts one?
Click to expand...
Click to collapse
Sorry , yes , i forgot to mention about that . yes i am about Xiaomi Parts

Hayastan said:
Sorry , yes , i forgot to mention about that . yes i am about Xiaomi Parts
Click to expand...
Click to collapse
Will look into it, in the meantime do you have any magisk modules? That can break sound enchantment?

CSAPawn said:
Will look into it, in the meantime do you have any magisk modules? That can break sound enchantment?
Click to expand...
Click to collapse
No i don't , only systemless hosts .

CSAPawn said:
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (OrangeFox Recovery recommended).
3. Wipe the System, Vendor, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest OrangeFox recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_xiaomi_ginkgoDevice tree source:
https://github.com/AICP/device_xiaomi_ginkgoVendor source:
AICP/proprietary_vendor_xiaomi
Contribute to AICP/proprietary_vendor_xiaomi development by creating an account on GitHub.
github.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
@Adithya R
@madmax7896
Information:
ROM OS Version: 11.x
Kernel: Linux 4.14
ROM Firmware required: Latest Firmware from MIUI 21.4.28 and up
Status: STABLE
Release Date: 05-20-2021
You want to see a "normal" night at the "DEV office", click here!!
Click to expand...
Click to collapse
Does AptX and LDAC work?

promethsuresh said:
Does AptX and LDAC work?
Click to expand...
Click to collapse
Don't know bout LDAC, but AptX worked flawless last time I ran the rom (some weeks ago).

NeoPreacher said:
Don't know bout LDAC, but AptX worked flawless last time I ran the rom (some weeks ago).
Click to expand...
Click to collapse
LDAC doesn't work

Hmm cant find anything related Xiaomi Parts in the changelog for 07/01/2022 build , but dirty flashed over previous build and now Audio Enchantment of Xiaomi Part works as expected )

Hello, does your rom support signature spoofing for microG ? thanks

[ROM][12.1]LineageOS 19 [with microG] for OnePlus 5 & 5T

How-to migrate from LineageOS for microG 19.1 to LOS Legacy for microG 19.1
See here :
[ROM][12.1]LineageOS 19 [with microG] for OnePlus 5 & 5T
With the rise of Big Tech and the encroachment of government on our lives, I felt more of a desire to move away from Google and the like. OnePlus 5/5T was built with microG and LineageOS source and is fully functional. What it is. It's LineageOS...
forum.xda-developers.com

Good work

how is battery life? the other custom roms have a massive battery drain.

Should be less since no gapps are used since microg is in build

Download for Oneplus 5 Cheeseburger ROM now available.
and I know that our certificate on the website has expired. the update can take up to 24 hours.
Go to accept.... to go to the download page.
or temporarily use this page
until the certificate is updated
Index of /dumpling
Index of /cheeseburger
28.04.2022 15:00 uhr
certificat restored everything works again as before

Hi, how can I install normal gapps with this rom? Or can I?
For e.g: uninstalling microg and installing the normal one.

Colleague but you have already asked in the Telegram group and you were told use the default ROM .
if you use my ROM and install gapps are removed microg .
and next update the gapps are overwritten and microg is back .
so it makes no sense what you are trying to do.
even if it should work there will be 90% bootloop

metahex12 said:
Hi, how can I install normal gapps with this rom? Or can I?
For e.g: uninstalling microg and installing the normal one.
Click to expand...
Click to collapse
is it because of what you wrote on Telegram that the developer of the standard ROM does not keep his ROM up to date that you want to use my ROM?
I use the same sources as the standard ROM just for info .

Exodusnick said:
Should be less since no gapps are used since microg is in build
Click to expand...
Click to collapse
the battery drain problem seems to be caused by a kernel issue with the modem. i assume that this rom uses the same kernel?

satand said:
the battery drain problem seems to be caused by a kernel issue with the modem. i assume that this rom uses the same kernel?
Click to expand...
Click to collapse
I have no problem of battery discharge.

Exodusnick said:
With the rise of Big Tech and the encroachment of government on our lives, I felt more of a desire to move away from Google and the like. OnePlus 5/5T was built with microG and LineageOS source and is fully functional.
What it is. It's LineageOS with all of Google's closed-source binaries removed and replaced with microG. I.e. no Play services or GAPPS. UnifiedNLP is used as the networking location provider instead of Google's NLP. Aurora Store and Aurora Droid is installed by default and provides an alternative app store. However, with the Aurora Store, you cannot install all Google Play Store apps such as buy apps. F-Droid can be installed through Aurora Droid if you need it .
Other information Google Play Store Alternative If you want to have full access to normal Android Play Store apps, After opening Aurora Store, select the appropriate option. usually option number 1 is the most commonly used with this ROM, unless changed by the user. After setup, you will have access to all apps as usual. Some apps require Play Services and cannot be used.
After installation - Open the microG app --> self-check sections should be successful. Location Services - By default, LocalGsmNlpBackend, which uses the NominatimGeocoderBackend, and NominatimNlpBackend, which uses Mapquest's Noninatim service, are disabled. Open the microG app --> location modules and enable the modules you want. Then restart the device.
It is strongly recommended not to install GApps as this ROM contains a replacement for them.
What everything works
all standard functions
What does not work
You tell me!
Important :Make a full backup of the system via twrp so that you can get back to your old version.
How To Install LineageOS recovery:
have never installed a rom with fastboot so I can not say if it works.....
- Flash Lineage recovery with fastboot if you don't have it yet (fastboot flash recovery recovery.img)
- Reboot to Lineage recovery
- Select ´Apply update´ -> ´Apply from adb´
- On PC, do ´adb sideload lineage.zip´
Clean flash
Installation Clean Via twrp
- Back up your data (recommended)
- Remove custom encryption pins/passwords (recommended)
- Boot into twrp go to Delete /Advanced - Wipe system / data / cache / vendor (do not format data - this will erase the internal memory) .
- back to the main menu go to install and find the location where you saved the rom.
- select the rom and then confirm reboot
Dirty flash (Update)
Dirty Flash (OTA) update can be downloaded from lineageos updates and installed on your device.
If it is not possible to install the update automatically, or if you want to install it manually, do the following,
select install in twrp/ parent folder/data/lineageos_updates select the rom install it and restart everything else you want to install.
how to boot into twrp from the system:
settings>system>keys> down to menu point on/off menu
then activate Advanced reboot.
now press the power button right , select reboot a second menu appears,
there you can select Recovery from and it will automatically boot into twrp.
Other information
Note that many features of LineageOS are not yet finished, this is not a device bug and please do not report them,
also do not file bug reports for known problems or bug reports without the correct
Do not publish bug reports without specifying logs (logcats) or steps to reproduce the bug.
a) Logcat
b) proc/last_kmsg
(or proc/kmsg)
c) data/tombstones
d) dmesg
Device name:
OnePlus 5 (cheeseburger)
OnePlus 5T (dumpling)
Rom Download OTA
dumpling
cheeseburger
some tests still need to be done
before I release them .
download recovery
dumpling-recovery.img
cheeseburger-recovery.img
download TWRP Offizial :
https://dl.twrp.me/cheeseburger_dumpling/
Download TWRP Unoffcial:
TWRP Unofficial v3.6.1 A11 Cheeseburger/Dumpling
Disclaimer: It does not decrypt A12 data,
only if the lock screen is removed (pin/pattern/password).
tested on op5 with PE12 / LOS 19.1 from Daywalk3r666 and The_Voice_70 and found to be suitable .
XDA Thread
Download Root:
Magisk v24.x
All credit goes to
T1mb3 , bananer and LineageOS
Contributors
Exodusnick
Rom tester
Daywalk3r666
The_Voice_70
microG Source code :
https://github.com/lineageos4microg
https://github.com/Exodusnick/android_vendor_partner_gms
LineageOS source code :
- https://github.com/LineageOS
Device tree:
- android_device_oneplus_cheeseburger
- android_device_oneplus_dumpling
- android_device_oneplus_msm8998-common
Kernel:
- android_kernel_oneplus_msm8998
Support for german users
forum.los-legacy.de
Telegram Group
t.me/losoneplus5
ROM OS Version: Android 12
ROM Kernel: Linux 4.4.x
Based On: LineageOS
Required firmware: OxygenOS 10.0.1
Version Information
Status: Stable
Created 2022-04-26
Last Updated 2022-04-26
Everyone is responsible for his own actions. Neither the operator of the site, nor I take responsibility for any damage to your device caused by any flash attempts.
Click to expand...
Click to collapse
Greetings...
Can You tell me if this GSI may be installed on a Samsung SM-A225M/DSN?
I Would like to try this one
Thanks in advance.

@Marcio.RS
What makes you think that this is a GSI ROM ?
This ROM is only for OnePlus 5/5t

Exodusnick said:
@Marcio.RS
What makes you think that this is a GSI Rom ?
It is only for OnePlus 5/5t
Click to expand...
Click to collapse
Thanks for your reply.
I was looking for a GSI for my A225M/DS and I thought your rom was a possible one.
Thanks for your answer once again!

@Marcio.RS
If it were one, I would call it that, but it is not. Sorry, I can't help you there.

Exodusnick said:
is it because of what you wrote on Telegram that the developer of the standard ROM does not keep his ROM up to date that you want to use my ROM?
I use the same sources as the standard ROM just for info .
Click to expand...
Click to collapse
Yes but I think you are fetching los sources more frequently with new builds?

@metahex12
No. on the contrary I do not proceed as linaeageos does.
I will only update if there are changes from the Dev. Standard Rom otherwise I only update every two to three weeks or only monthly if the security pacht is available.
Why should I waste resources and release a new update every week like lineageos does ?
Check my OTA download page to see that I don't release updates every week.

satand said:
the battery drain problem seems to be caused by a kernel issue with the modem. i assume that this rom uses the same kernel?
Click to expand...
Click to collapse
use the same kernel as the default Rom, see OP Thread.

Exodusnick said:
use the same kernel as the default Rom, see OP Thread.
Click to expand...
Click to collapse
On one night i left the phone on, and the battery drained. Another night i turn on flight mode and it was fine...
There's a annoying seedvault back up, how do we stop it?

In App Settings force the Seedvault to quit and clear cache and data.

Develop Bugs

welcome