[9][OFFICIAL][RELEASE][r71] CarbonROM | cr-7.0 [i9100]

[9][OFFICIAL][RELEASE][r71] CarbonROM | cr-7.0 [i9100] - Galaxy S II Android Development

FAQ
0) Known issues:
- Call recording only records microphone
- Device encryption [I have no idea how to fix it, sorry]
1) Yes, it is rootless.
Do not ask me when it will have implementation for compatibility with the old SuperSU application. Do not insist.
2) Magisk:
Adaptation possible! But to be successful I have to synchronize the cr-7.0 code on the PC and 150GB of space is needed, which I don't have at the moment.
As soon as I can, I'll do it.
DON'T ASK ME WHEN, PLEASE.
The i9100 Kernel (3.0.101) does not support namespace to work. Please, do not pollute the topic with that kind of question.
3) Bugs:
Did you find a bug or problem?
Make a logcat and put it in pastebin/hastebin. I'll look when I can
You will need a computer, adb installed, usb debugging enabled on the smartphone and a usb cable.
Here's how to do it here.
1. Open Command Prompt (Windows) or Terminal (Linux/macOS).
2. Type:
Code:
adb logcat -d > carbon-logcat-dateoflogcat.txt
This will save the log to carbon-logcat-dateoflogcat.txt.
4) MindTheGapps or NanoDroid MicroG?
Does not matter! But... the NanoDroid is lighter. Recommend!
5) I love MicroG, but I also like the Play Store
No problems! After MicroG installation, you can use this Shadow53 installer for store use.
P.S: This should be done after you have restarted the device with NanoDroid installed.
6) Why use the dark mode to prevent wear on the AMOLED screen?
8 years baby! You will not want to put a generic on your cell phone, right?

Upgrade from Samsung stock ROM to latest build using ODIN 3.13.1
Also recommended for devices with Android 4.4 - 5+
OBS1: Read before you get started!
OBS2: If you previously used LineageOS 16.0 build #15, skip to step 4.
OBS3: Back up your files and make a full wipe before the procedure.
Files Required:
Stock ROM
Pit file by-the.gangster
Samsung USB Driver
Odin 3.13.1
Latest CarbonROM
Pit file with Emulated Storage by rINanDO
TWRP Emulated Storage 3.3.1-1 by rINanDO
0) Install Stock ROM
0.1 After downloading the tools, install the Samsung USB Driver and unzip the file of the rom.
The original rom file is tar.md5
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.
0.3 In the pit tab on the left side, select the file "i9100_1.5gb-system_6gb-data_512mb-preload_by-the.gangster.pit"
0.4 In AP button, select the tar.md5 file. The Odin app will frozen for a few minutes but do not worry.
After this, select start button. Wait terminate, do not pull the cable
0.5 The device will restart. A message will appear stating that it is encrypted. Turn off your device and enter recovery mode (Volume up + Power/Standby + Home and hold for 10 seconds). Clear Cache and Dalvik / Cache. Restart.
0.6 A warning will appear in the status bar saying that the partition is corrupted. Format the partition. Verify that the partition succeeded in the device settings.
0.7 Charge the phone and follow the next instructions.
1) Prepare your phone
1.1 Copy the ROM to the Micro-SDCard before flashing.
1.2 Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
1.3 Start Odin 3.13.1 in your PC.
1.4 Connect your phone via USB to your PC.
1.5 Press volume up on your phone, Odin should detect your phone.
2) Odin
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
AP : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
Press Start.
3) After successful flash
Reboot phone into Recovery
Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1. Swipe to allow modifications.
4) TWRP
In TWRP 3.3.1-1 you need to format partitions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
Dalvik / ART Cache
Cache
System
Non-emulated Storage
-> Swipe to Wipe
5) Install CarbonROM and boot system.
P.S: To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again

Mercy.

Changelog - Here you will be updated if you have relevant information
OBS:
1) Don't use 20190911 build due to partition issues.
2) Automatic date/time of build 20200920 does not work and crashes after 2/3 days.
Use the latest build to make sure it works.
30082021 (Official build)
Updated sources
Android 9.0.0_r71
August 2021 Security patch
10072021 (Official build)
Updated sources
Android 9.0.0_r69
June 2021 Security patch
20092020 (Official build)
Updated sources
Android 9.0.0_r59
August 2020 Security patch
02032020 (Official build)
Updated sources
February 2020 Security patch
20122019 (Official build)
Updated sources
December Security patch
Added support for exFAT + NTFS (Thanks to @TALUAtXDA)
02102019 (Official build)
Disabled Multicast DNS
Performance: Disabled Kernel Samepage Merging
Resize userdata partition to leave room for the crypto footer region
Updates by rINanDO:
Fix unlocking SIM PIN
Fixed color issues in screen recording
14082019 (Official build)
August security patch
SamsungDoze: Fix menu display
31072019 (Official build)
After four months of testing, the official compilation was released. Enjoy!
15072019
July security patch
Fixed turn on the screen via home button
Updates by rINanDO:
Set swappiness to 100
Using Preload-partition for misc
Added Bluetooth SIM Access Profile support (Not tested)
Fixed stereo microphone recording (also in videorecording)
Fix autofocus in preview
Set ro.config.small_battery to true. This will trigger device-idle in 15
minutes instead of 30 minutes
09062019
Initial release

https://get.carbonrom.org/device-i9100.html
Is the official version your job?

ze7zez said:
https://get.carbonrom.org/device-i9100.html
Is the official version your job?
Click to expand...
Click to collapse
Yes! Now it's official

linusdan said:
After four months of testing, the official compilation was released. Enjoy!
Click to expand...
Click to collapse
Hi linusdan ! I don't guess , Does your Carbon ROM (latest release) have root in it ?
or should be do separately ? where is the complete guide to root with Carbon ROM ?
Thanks for your Job

Czeh said:
Hi linusdan ! I don't guess , Does your Carbon ROM (latest release) have root in it ?
or should be do separately ? where is the complete guide to root with Carbon ROM ?
Thanks for your Job
Click to expand...
Click to collapse
It is without root, as said in the second post. LineageSU does not work.

On stock ROM i9100 (there was never anything else) I made an instruction with post #3 but nothing happens.
My system is Windows 10 PRO.
Edit.
===
Instead:
0.2 Start Odin and connect your phone to the PC. The device ID will appear in the application interface.
It should be:
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.

ze7zez said:
Instead:
0.2 Start Odin and connect your phone to the PC. The device ID will appear in the application interface.
It should be:
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.
Click to expand...
Click to collapse
Fixed! Thanks :highfive:

giving this a try @linusdan, switching from your pixel experience
---------- Post added at 07:54 PM ---------- Previous post was at 07:04 PM ----------
installed with NanoDroid Micro G. Much fast than PE
found settings is crashing on clicking ambient display..no show stopped though, will post logs in a while

chhapil said:
found settings is crashing on clicking ambient display..no show stopped though, will post logs in a while
Click to expand...
Click to collapse
This is not a crash, just an incorrect redirection.
Enter "ambient" in the settings browser and open.
It works.

used with both gapps and microG.
MicroG is really recommended... with GApps the phone just crawls while microG is fast enough for daily driver!

chhapil said:
Found settings is crashing on clicking ambient display..no show stopped though, will post logs in a while
Click to expand...
Click to collapse
ze7zez said:
This is not a crash, just an incorrect redirection.
Enter "ambient" in the settings browser and open.
It works.
Click to expand...
Click to collapse
SamsungDoze factoring was wrong. The patch will be inserted in the next build via OTA.

linusdan said:
SamsungDoze factoring was wrong. The patch will be inserted in the next build via OTA.
Click to expand...
Click to collapse
What is your build cycle for carbon rom currently?

chhapil said:
What is your build cycle for carbon rom currently?
Click to expand...
Click to collapse
Wednesdays at 2AM GMT
Sync failed and there was no compilation of the week. I am checking what the problem is.

linusdan said:
Wednesdays at 2AM GMT
Sync failed and there was no compilation of the week. I am checking what the problem is.
Click to expand...
Click to collapse
Thanks, we've got a new Carbon. :good:
OTA update has gone through without problems.

Supersu
What happens when you flash supersu flashable with TWRP? Would it not boot?

roynatech said:
What happens when you flash supersu flashable with TWRP? Would it not boot?
Click to expand...
Click to collapse
Bootloop. The reason is described in the thread.

Related

[ROM][UNOFFICIAL][7.1.2] LineageOS 14.1 [trlte][trlteduos]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 3 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
BasketBuild Downloader
- daktak
In the app's Settings, change Project to ripee and Device to trlte or trlteduos. Under Base Url, replace s with www.
ROMs
ripee (LineageOS su root included.)
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
_mone
- LineageOS
LineageOS Extras
- addonsu-14.1-arm-signed.zip
- addonsu-remove-14.1-arm-signed.zip
Magisk
OpenGapps Downloader
- daktak
Open GApps
- pico
Aroma-Extras
- Creeper36
The SELinux Switch
- Ibuprophen
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS 13.0, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 14.1 variant, which corresponds to the model of your phone!
How to flash a bootloader and/or modem and TWRP1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
3. Download the .tar file of the latest version of TWRP from the link above,
4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.
How to flash LineageOS, Open GApps, and Aroma-ExtrasFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external microsd storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
How to install SPenCommand1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
2. Reboot into System,
3. Install SPenCommand.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation
1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps or Aroma-Extras over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Important information about stock S Pen functionality!The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
Bugs
- The fingerprint scanner works, but you have to go through the finger adding process twice for each finger!
- The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
- Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not yet supported.
- You tell us!
Credits
- cvxda, jef_00, lilferraro, and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the trlte and trlteduos.
Sources
- _mone
- Corinna Vinschen
- fattire
- LineageOS
- ripee
- samsung-apq8084
XDA:DevDB Information
LineageOS 14.1 , ROM for the Samsung Galaxy Note 4
Contributors
jef_00, _mone, ripee, fattire
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Created 2017-04-13
Last Updated 2019-07-13

Reserved

Reserved

this build is special for @ripee
changelog:
fixed recent view borders

jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.

Does this work with the 910T? Any support for 10,000mAh battery?

ripee said:
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.
Click to expand...
Click to collapse
No problem mate! @ripee

Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
Not yet sorry!

Can anyone make data for tmobile N4?
Sent from my SM-G935F using XDA-Developers Legacy app

@jef_00
_mone said:
Clone, fork, rebase, merge, do whatever you want with the repos, but please share it; we are here for that!
Click to expand...
Click to collapse
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.

Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
jef_00 said:
Not yet sorry!
Click to expand...
Click to collapse
Is that no on the 910T, or no on the 10 AH battery?
I have a 910T and would love to try this build.
Didn't the trltexx CM build work on the 910T?

I had some time to flash build 01/11. The recent tiles are definitely fixed!
I guess now attention can be turned to the fingerprint scanner?
I also noticed that the setting to have the display save power is missing from LiveDisplay, the one usually at the bottom of that submenu.
Thank you @jef_00!

_mone said:
@jef_00
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.
Click to expand...
Click to collapse
it is done sorry about copy/paste

Just flashed the ROM, wiped cache/dalvik cache and booted.
First impressions:
-Turning the screen on is quite slow like on all non-TouchWiz roms I've tried in the past compared to TW roms (I come from x-rom Note7 port rom). Unlike CM13 on the LG G2
I have no idea why no one talks about this. It takes around 1.4 seconds to show the lockscreen, around 40% more than stock roms.
-Low volume when listening to voice clip recorded by myself on Whatsapp from earpiece
-During the first 15 minutes with the phone I experienced constant freezings (3+ sec. duration) very often while scrolling anywhere. Settings app seems to stop responding too often, perhaps it's related to the freezings. However, right now as I'm writing this I don't seem to be experiencing them anymore...
-After using the phone for 30+ minutes the automatic rotation stops working (only works on camera app).
-Half the translation is in English instead of in Spanish some of which are erratic (Under Gestures: "Proximity wake up: wake up when shaking the phone". Those are two different things.)
- No way to set a different vibration intensity on capacitive buttons (too strong by default IMO).
-Duplicate contacts on DIALER APP (due to having contacts on whatsapp). Went to contacts app-->contacts to show--> set only Google contacts and they stop showing duplicated only on contact app, not on the dialer app. You did it again Google! I saw this stupid behavior back in CM13.
Things I liked/surprised me:
-Built-in option to disable home button from waking up the device.
-Show notifications (black and white screen, ideal for amoled screen phones) when uncovering proximity sensor.
-Speed in general.

The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.

ripee said:
The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.
Click to expand...
Click to collapse
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.

aLexzkter said:
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.
Click to expand...
Click to collapse
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.

ripee said:
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.
Click to expand...
Click to collapse
I experienced it on all 6.0.1 aosp roms too...

Tanks for this ROM!!!
jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.

SUREFACE said:
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.
Click to expand...
Click to collapse
glad you are back!!

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][tblte][trlteduos]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-15.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 4 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP for Samsung Galaxy Note 4 (Qualcomm)
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
Open GApps
OFFICIAL !!
I am not building for oreo anymore, devs have moved to pie,
thanks everyone !!
tripLr
Code:
LAST ROM Downloads for Oreo
triplr
Source Code http://www.github.com/tripLr
@kevintm78 kernel development
https://forum.xda-developers.com/note-4/snapdragon-dev/kernel-flashpoint-v3-1-stock-n7-ports-t-t3727407
(LineageOS su root included.)
ROMs Note 4
SM-N910F/G/P/R4/T/T3/V/W8:
click to open trlte drive folder
https://drive.google.com/drive/folders/1XWrdmxHeC0A7zGK-TGOH3XG2VfKYP-IA?usp=sharing
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 Edge
Note 4 Edge Thanks to @micky387 and @ripee
Which device is supported ??
I'm do the best for support multi note edge device so tell me if you see an issue and write it here with you variant
Support SM-N915F SM-N915FY SM-N915G SM-N915T SM-N915P SM-N915V
Click to expand...
Click to collapse
Google Drive Download Folder Click to open and browse to latest
https://drive.google.com/drive/folders/1lD5vLRFYr8XyGIgL2oT9VXFmdcLOWe3F?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 DUOS
- SM-N9100ZC/ZH/6W/9W:
click to open trlte duos folder
https://drive.google.com/drive/folders/1uibdRnVs9-klbJhtvB5__5B9XFYel1jK?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
Code:
# Depreciated
[B]ripee[/B] [I]([COLOR="Teal"]LineageOS[/COLOR] su root included.)[/I]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31259"][B]
lineage-15.1-20190218-UNOFFICIAL-trlte.zip[/B][/URL]
- SM-N9100ZC/ZH/6W/9W: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31260"][B]
lineage-15.1-20190218-UNOFFICIAL-trlteduos.zip[/B][/URL]
[B]_mone[/B]
- [URL="https://androidfilehost.com/?w=files&flid=140308&sort_by=date&sort_dir=DESC"][B]LineageOS[/B][/URL]
[B]micky387[/B]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://androidfilehost.com/?w=files&flid=257279&sort_by=date&sort_dir=DESC"][B]Note 4[/B][/URL]
[/CODE]LineageOS Extras
- addonsu-15.1-arm-signed.zip
- addonsu-remove-15.1-arm-signed.zip
Magisk
The SELinux Switch
- Ibuprophen
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 15.1 variant, which corresponds to the model of your phone!
How to flash a bootloader and/or modem and TWRP1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
3. Download the .tar file of the latest version of TWRP from the link above,
4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.
How to flash LineageOS and Open GAppsFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Important information about stock S Pen functionality!The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
How to install SPenCommand1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
2. Reboot into System,
3. Install SPenCommand.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Temporary fix for random SIM death on all trlte variants, courtesy of _mone: boot-1223-trlte.img
- The fingerprint scanner has not yet been integrated into either trlte or trlteduos.
- The front camera force closes, requiring a reboot to work again.
- Bluetooth does not see some wearable devices.
- The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
- Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not (yet) supported.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- fattire and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the trlte and trlteduos.
Sources
- LineageOS
- triplr-dev
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy Note 4
Contributors
micky387, ripee, tripLr, _mone, cvxda
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Snapshot
Current Stable Version: 8.1.0
Created 2018-03-09
Last Updated 2019-07-13

Reserved

Reserved

known bugs?

Rom for note 4 duos N9100???

I am gonna test it now on N910T and will report back.
Thank you.
.
By the way i got some cool amoled wallpapers of lineage os below.

Thx ,keep the note 4 alive ,I will try this weekend

aafranki said:
known bugs?
Click to expand...
Click to collapse
Some camera issue (minor) and ??
merc200k said:
Rom for note 4 duos N9100???
Click to expand...
Click to collapse
Not support
Trex888 said:
I am gonna test it now on N910T and will report back.
Thank you.
Click to expand...
Click to collapse
Perfect ,report after
Becareful read closely OP.
When @ripee or @_mone are ready , they will continue this project

not support N9100??? so I cant test it..
maybe in the future?

Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.

Fingerprint dosnt work.No sound too.

Sound is not in this package

nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
bt don't work, call sound don't work, speaker sound don't work= phone inusable

petzku said:
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Click to expand...
Click to collapse
scpeter1 said:
Fingerprint dosnt work.No sound too.
Click to expand...
Click to collapse
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
Yes ,error in script.
Upload in progress with new build.
Sorry for this mistake

aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
That's right but I am jockeying a little the dev well fix this in the next update

nisi3nt said:
That's right but I am jockeying a little the dev well fix this in the next update
Click to expand...
Click to collapse
Yes, Done. New build available in Op
Sorry again

micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
download link?

hmm link dosen work error 404

micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
Rom dl Link not working.

Fingerprint dosntworking again.Sound is back.

[ROM][EOL][FINAL][8.1.0][i9100] Pixel Experience ASB[AOSP][r65][2019/07/15]

{
"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"
}
PixelExperience ASB for Galaxy S2 [i9100]
What is this?
Pixel Experience ASB is an AOSP ROM based on the original project, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device and latest ASB patches for Android Oreo
Based on Android 8.1
NOTE:
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* 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.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Lights
Sound / vibration
Known issues
VSync
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
AFH: New builds
Old builds without emulated storage

Android OS version: 8.1.0_r65
Security patch level: July 2019 (Lineage ASB)
Build author: linusdan
Source code: https://github.com/PixelExperience
Kernel of device: https://gitlab.com/linusdan/kernel_samsung_smdk4412/tree/oreo
ROM Developer: linusdan
Credits - @rINanDO
Before installing ROM, you need to:
- 1.5 GB of system partition
- Emulated storage (from the April build).
Not sure how? See in this post
If you like my work, do not forget to click the button thanks. It's free!!!
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.0.x
Based On: AOSP
TWRP Required: TWRP 3.3.1-1 EMU
Version Information
Status: Stable. No longer maintained
Created 2018-09-21
Last Updated 2019-07-15

Reserved
NO ETA REQUESTS!
DOWNLOAD LINKS IN OP
Frequent questions
I do not use GAPPS! How can I remove?
R: Unfortunately not. Sorry.
What are the bugs?
R: See Known issues in OP.
How do I get root?
R: Download SuperSU Flashable and install via TWRP. After this, update the application by the Google Play
I found a bug!
Make a logcat and put it in pastebin/hastebin. I'll look when I can
You will need a computer, adb installed, usb debugging enabled on the smartphone and a usb cable.
Here's how to do it here.
1. Open Command Prompt (Windows) or Terminal (Linux/macOS).
2. Type:
Code:
adb logcat -d > logcat-dd-mm-yyyy.txt
This will save the log to logcat-dd-mm-yyyy.txt.
No nonsense questions, please!
Avoid meaningless discussions and help you and the user have useful information on the thread :good:
Dan, when I connect the phone to the PC, I can not access the files because there is no information to authorize the procedure in the notification! Please take a look when you can.
Calm down, Padawan! This is not a bug but google stuff. They have placed the authorization option on development tools. Everyone is trying to understand why this
Do this when you want to have access to them:
Go to System -> developer option -> USB and activate MTP manually.
What will be the frequency of compilations?
Monthly or every two months . I plan to spend $12 per month for the projects.
Praying for the low dollar quote on the Google Cloud Engine :laugh::fingers-crossed::good:

Upgrade from Samsung stock ROM to latest build using ODIN 3.13.1
Also recommended for devices with Android 4.4 - 5+
Back up your files and make a full wipe before the procedure.
Files Required:
Stock ROM
Pit file by-the.gangster
Samsung USB Driver
Odin 3.13.1
Latest Pixel Experience
Pit file with Emulated Storage by rINanDO
TWRP Emulated Storage 3.3.1-1 by rINanDO
0) Install Stock ROM
0.1 After downloading the tools, install the Samsung USB Driver and unzip the file of the rom.
The original rom file is tar.md5
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.
0.3 In the pit tab on the left side, select the file "i9100_1.5gb-system_6gb-data_512mb-preload_by-the.gangster.pit"
0.4 In AP button, select the tar.md5 file. The Odin app will frozen for a few minutes but do not worry.
After this, select start button. Wait terminate, do not pull the cable
0.5 The device will restart. A message will appear stating that it is encrypted. Turn off your device and enter recovery mode (Volume up + Power/Standby + Home and hold for 10 seconds). Clear Cache and Dalvik / Cache. Restart.
0.6 A warning will appear in the status bar saying that the partition is corrupted. Format the partition. Verify that the partition succeeded in the device settings.
0.7 Charge the phone and follow the next instructions.
1) Prepare your phone
1.1 Copy the ROM to the Micro-SDCard before flashing.
1.2 Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
1.3 Start Odin 3.13.1 in your PC.
1.4 Connect your phone via USB to your PC.
1.5 Press volume up on your phone, Odin should detect your phone.
2) Odin
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
AP : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
Press Start.
3) After successful flash
Reboot phone into Recovery
Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1. Swipe to allow modifications.
4) TWRP
In TWRP 3.3.1-1 you need to format partitions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
Dalvik / ART Cache
Cache
System
Non-emulated Storage
-> Swipe to Wipe
5) Install Pixel Experience and boot system.
P.S: To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
Changelog
15072019 [EOL] - FINAL BUILD
* Android 8.1.0_r65
* Fix audio stereo recording
* GApps updated to the latest
* Add dummy keydisabler to allow navbar disabling
* Chromium webview: Updated to 75.0.3770.101 via LOS;
* Added Bluetooth SIM Access Profile support (not tested)
* Using the preload partition for compatibility with the new version of TWRP Emulated Storage by rINanDO
* Applied security updates from LineageOS (July 2019) because Google has not released a new tag for the Oreo
Important:
Update the TWRP before installation!
Files Required:
TWRP EMU 3.3.1-1 by rINanDO
1) Flash TWRP EMU 3.3.1-1 by rINanDO and reboot recovery.
2) Install the new update with dirty flash.
Changelog
04062019 [EOL]
* Android 8.1.0_r65
* GApps updated to the latest
* Fix ADB connection via FunctionFS
* Chromium webview: Updated to 72.0.3626.121 via LOS;
09042019 [EOL]
First PixelExperience ASB build
* Android 8.1.0_r63
* Increased heapsize to 360mb
* Support to multi user added
* GApps updated to the latest
* Performance enhancements
* Emulated storage implemented
* Ported FunctionFS to our kernel (credits goes to @rINanDO)
24112018
* Updated sources;
* GApps updated to the latest
* Fix brightness button;
* Various bug fixes.
07112018
* Updated sources;
* GApps updated to the latest
13102018
* Enabled wifi powersave mode (credits goes to @rINanDO)
* Chromium webview: Updated to 69.0.3497.109 through the lineageos repository;
* GApps updated to the latest
04102018
* Performance optimizations;
* Implementation of auto sleep through (battery drain has improved a lot!);
* GApps updated to the latest

ohh!! i was waiting for this!!
thanks
i'll try and report

thanks alot for share :good:
but if this is a beta, i think it's better add BETA in title

linusdan said:
PixelExperience for Samsung Galaxy SII International (GT-I9100)
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
GDrive - AFH
Last Updated 2018-09-21
Click to expand...
Click to collapse
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?

I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash

guest4711 said:
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?
Click to expand...
Click to collapse
chhapil said:
I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash
Click to expand...
Click to collapse
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please

linusdan said:
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please
Click to expand...
Click to collapse
Sure will help as normally pixel ROMs come with gapps pre packaged it needs bigger system partition.
Also i have seen from Moto G forum, folks have seen better results with Android Go config.
Worth a try for our old device

linusdan said:
INSTRUCTIONS FOR RESIZING THE PARTITION
2) Open the odin. In the pit tab on the left side, select the file "I9100_1.5GB-System_6GB-Data_512MB-Preload_by-
Click to expand...
Click to collapse
Do you recommend that pit files for all yours ROMs? For Nougat too?

Gastozz said:
Do you recommend that pit files for all yours ROMs? For Nougat too?
Click to expand...
Click to collapse
And why not?

Thanks, Feedback as soon as possible

New build is up with Android Go configurations.
Download in OP.

-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys

islander999 said:
-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys
Click to expand...
Click to collapse
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!

linusdan said:
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!
Click to expand...
Click to collapse
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?

islander999 said:
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?
Click to expand...
Click to collapse
Yes! A thorough cleaning is always recommended.

linusdan said:
Yes! A thorough cleaning is always recommended.
Click to expand...
Click to collapse
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example

islander999 said:
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example
Click to expand...
Click to collapse
If you wish.

https://forum.xda-developers.com/showthread.php?t=3752664 go apps it works on dotos v2.5 oreo

[ROM][DISCONTINUED][9] LineageOS 16.0 [tblte][trlte][trlteduos]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant under the links in the TWRP thread. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 5 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Open GApps
ROMs
triplr
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
- SM-N915F/G/P/R4/T/W8: tblte
_mone
- LineageOS
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 16.0 variant, which corresponds to the model of your phone!
How to flash LineageOS and Open GAppsFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Important information about stock S Pen functionality!The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not supported, and will not be supported for the foreseeable future.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Our resident Developer Emeritus fattire and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the tblte, trlte, and trlteduos.
Sources
- LineageOS
- apq8084
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy Note 4
Contributors
ripee, _mone, mobspyguy, khalvat, cvxda, tripLr
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-02-16
Created 2019-02-16
Last Updated 2020-04-04

Reserved
Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.

Reserved

Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.

hamid6831 said:
Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.
Click to expand...
Click to collapse
As has been explained in every Qualcomm thread, what you are asking for is like trying to grow oranges using tomato seeds. Please contact the appropriate dev in the appropriate forum about Exynos support.

It's not really important at all, but is there a way to change the boot logo on this ROM (the Galaxy Note 4 logo displayed when starting the phone)? I tried to extract param.bin, it didn't work

Rom , after a total clean flash with Open Pico Gapps and Magisk 18.1, has booted up in just 2 minutes.
Android setup finished in less than a minute.
No hick ups, no errors.
Everything has run smooth and fast.
This is a job very well done.
Thank you all for taking us to the next level of Android.
Thank you @ripee, thank you @_mone , thank you @mobspyguy

Unofficial lineageos pie superuser add on
https://androidfilehost.com/?fid=11410963190603875495
Works on my tab s2
Credit
https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-16-0-t3833953/page1

Lets have a look inside it

holy crap, will be trying this asap

piemanny said:
holy crap, will be trying this asap
Click to expand...
Click to collapse
Love your username
---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------
First time I have ever seen ALL MY WIFI
Without having to edit nvram_net.txt
Had a issue installing from a otg.
WiFi is extremely fast on 5gz.
Downloading my gapps.
Sofar what I need works with ROM only.
Awesome
---------- Post added at 11:00 PM ---------- Previous post was at 10:21 PM ----------
FYI, when installing without su or any gapps, root may be enabled for adb in developer mode. Don't know what it does but the selection is there.

Stock ROM no gapps
Everything works
Except ... Fingerprint
And low mic volume
Still wow.
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works

tripLr said:
Stock ROM no gapps
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works
Click to expand...
Click to collapse
Here same strange thing.
Typing message in XDA App and cannt really see what you type.
after a while, or when hit ender, letters show up..
Pico Gapps with magisk, battery foul.
So, its not battery related, or root.

logosA said:
Lets have a look inside it
Click to expand...
Click to collapse
Can I add these to the OP?

ripee said:
Can I add these to the OP?
Click to expand...
Click to collapse
of cource you can.
Its your work after all

logosA said:
of cource you can.
Its your work after all
Click to expand...
Click to collapse
Thanks but it's _mone's and mobspyguy's work

Sim Death....or No Service
For what its worth, even with an earlier modem (and i even rolled back the 1st 6.0.1 modem available for my region N910GDTU1DPF4), i still get the occasional sim death..not quite as bad as on Oero though
Usually i would manually reset the Ril Daemon via RIl Control from F-Droid
Today i finally got tired of doing this manually and set out to automate ril restarting with tasker
Please note i have never used Tasker before, so my shared profile may be less than ideal, im open for suggestions from more seasoned users, but for me it works well enough, or it seems to....
Tasker profile removed - it just wasnt as effective as Automate, harder to use, and unreliable in its State function....
Meanwhile i have been using Automate and testing this Automate flow i cobbled together - Updated 19/02/19 (similar to Tasker, but waaay easier to work with, flowchart based...) It currently checks for mobile connectivity every 5 minutes, and restarts ril-daemon if needed
The Automate way seems to be working better than Tasker....like u said I've not used Tasker before, and its horribly complicated compared to Automate...
Update: As of using my last Automate flowchart (updated above this morning), i have had zero sim death, dunno why, maybe polling connectivity every 5 minutes is enough to stop sim death, it hasnt gotten as far as the ril-daemon restart so far...will update if it does....
Of course, i spoke too soon, and jinxed myself
An hour after my last update i finally had my first sim death/ril-daemon reset...still, it was automatically recovered

I've tried this and mobspyguy's rom. the problem I have is that in my area I have good lte and data signal with these roms. But for some reason I have to drive 3 miles out of town before I can make a call. I'm on N910v straight talk on verizon network. P. S. The data works great while I'm at home just can't make calls.

Anyone run into SDCard showing as corrupted

ninja_unmatched said:
Anyone run into SDCard showing as corrupted
Click to expand...
Click to collapse
Although this shouldn't be the case, going from one version to another, your sd card can usually be expected to work best when you format it with the new version.

[ROM][UNOFFICIAL][12][OTA][OSS] LineageOS 19.1 for Galaxy Note9 Exynos

Requirements:
Latest firmware
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk

This build does not use the stock vendor, instead it's built on top of new trees, which have been worked on for some time. The source is on our github, link in OP. You also get a few neat features like fingerprint gestures, and bixby button that actually works with both normal and long press.
I suggest using OpenCamera since stock one has some issues with flash.
These builds are signed with our release keys.
star2lte and crownlte support will come a bit later as i don't own the devices, but they will be supported eventually.
THESE BUILDS HAVE FORCE ENCRYPTION ENABLED, AND ONLY LINEAGE RECOVERY IS SUPPORTED. THESE THINGS WILL NOT CHANGE. IF YOU DON'T USE LINEAGE RECOVERY, AND SUFFER FROM DATA LOSS, DON'T COMPLAIN HERE.

how to restore to TWRP recovery, when flashed lineage recovery

Thank you for your hardwork!!! <3

Does banking apps work with this rom

lythongac said:
how to restore to TWRP recovery, when flashed lineage recovery
Click to expand...
Click to collapse
just Odin + TWRP (in tar) on rebooted Download mode
@DeHuMaNiZeD
Good work ! Work very well !
Is it possible to Add Dual Sim (crownlte) ?

My 1 week review as daily use :
1. smooth, stable (uptime 122h)
2. Wifi, bluetooth OK (no problem)
3. battery ok, nothing special, at the end of the day, with call and nomal usage (3-4h screen on with youtube (on browser) and video call with jitsi) >50%
4. (i don't use anything from google)
just perfect for me !
thank you @DeHuMaNiZeD very good job !

I am struggling to flash "Flash lineage recovery" .
I am trying to flash recovery.img before which it has to be added to .tar. But the tar file that i am creating using 7zip is not working. Can you please guide how to create tar file from recovery.img to be flashed through ODIN.

sherry9oct said:
I am struggling to flash "Flash lineage recovery" .
I am trying to flash recovery.img before which it has to be added to .tar. But the tar file that i am creating using 7zip is not working. Can you please guide how to create tar file from recovery.img to be flashed through ODIN.
Click to expand...
Click to collapse
if you have TWRP you can just flash lineage recovery via twrp, no PC needed.

Any way to activate the dual sim ?
root > edit a file ?

New build is up

DeHuMaNiZeD said:
New build is up
Click to expand...
Click to collapse
Thank you for the effort!
I had a boot loop when I updated to this build.
I tried to reflash through ADB twice, but still boot-looping. Had to go back to build 20220219.
Any suggestions?
I did not flash the recovery partition again - is it necessary?

EGYLOGGEF said:
Thank you for the effort!
I had a boot loop when I updated to this build.
I tried to reflash through ADB twice, but still boot-looping. Had to go back to build 20220219.
Any suggestions?
I did not flash the recovery partition again - is it necessary?
Click to expand...
Click to collapse
I did not have any issue when replacing stock fw with this latest build. Used Lineage recovery to clear data/cache and installed via adb. No boot-loops. Very smooth.

loci said:
I did not have any issue when replacing stock fw with this latest build. Used Lineage recovery to clear data/cache and installed via adb. No boot-loops. Very smooth.
Click to expand...
Click to collapse
Same here, can confirm. Only problem i got was flashing lineage recovery with odin ( unrooted stock fw ), so i flashed twrp and then from twrp flashed lineage recovery . This is one snappy motherflicker

E2001: Failed to update odm image :/

Can you provide a local_manifest to build yourself for crownlte (19, 19.1) please?
Thanks..

Is it possible to get an answer here?
...

How to use SPen with this rom ?

dr_root85 said:
How to use SPen with this rom ?
Click to expand...
Click to collapse
Samsung proprietary feature. Wont work on AOSP ROMs. There are patched apks available for Samsung health and Wearable but not for S-Pen.

Better Mobile App

welcome