[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo] - Nexus 7 (2013) Android Development

[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo] - Nexus 7 (2013) Android Development

Reserved

Reserved

Awesome! Keep up the great work and thank you for keeping this devices development alive

JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911

oh yeah maga
make android great again

Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?

DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.

Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !

gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?

ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course

To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.

Thx!
Will test this ROM!

yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.

Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?

hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.

ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.

Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?

The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.

hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.

Related

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [I9515][I9515L]

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 version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
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 Galaxy S4 Value Edition over 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: Will the jfvelte ever receive official builds from LineageOS?
A: In short, no. The reason is that, in order to get a modern version of Android working properly on an ageing device, some recent commits needed to have been reverted and some legacy commits needed to have been re-introduced into the current source branch. These include a fix for something as fundamental as video recording with both the AOSP and 3rd party camera apps.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
If the first Oreo build you are flashing is 0220 or later, please clean flash it, as some users have reported problems with dirty flashing builds from 0220 or later over top of builds older than 0220.
ROMs
Exodusnick
Build files downloaded with the OTA updater can be found in /data/lineageos.updater. New builds are released weekly.
-
YouTube Video
Magisk
recommended Gapps Pico or Nano ARM 8.1
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 LineageOS 15.1!
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.
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
Bluetooth calls
- You tell us!
Changelog
All major features and bug fixes are discussed by Exodusnick and ripee in this thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- sombree and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the jfvelte.
Join us on Telegram[/URL], courtesy of Exodusnick!
Sources
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy S4
Contributors
Exodusnick
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Stock KitKat for your variant.
Version Information
Status: Stable
Current Stable Version: 8.1.0
Stable Release Date: 2019-05-17
Created 2018-12-29
Last Updated 2019-06-19

Reserved

Reserved

deleted

Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.

adarshadhungel1 said:
Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.
Click to expand...
Click to collapse
You are no doubt correct, but at this stage we are re-building the sources in the lineage-15.1 branch, for which there are currently none. Once we figure that out, we'll take a look at Go.

wifi is not working.
Is there a workaround for it ?

blunatic said:
wifi is not working.
Is there a workaround for it ?
Click to expand...
Click to collapse
Read the OP please. This rom is a WIP.

hello I have this very good equipment the update towards lack since android already goes for its version 9 if I would like to know the wifi for when it will be?? thanks.

hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?

Kelbimiguel said:
hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?
Click to expand...
Click to collapse
Which build did you try installing?

Don't installation
with this ROM I observed that it is the most recent

lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"

Kelbimiguel said:
lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"
Click to expand...
Click to collapse
Ok thank you for your feedback. I will delete this build.
When I am ready with another build, I will let you know.

Installed
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...

Kelbimiguel said:
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...
Click to expand...
Click to collapse
Yes, this build works, unfortunately we lost the copy of the sources, and I'm trying to re-create exactly what we did to make 1208 work.

lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip

hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...

Kelbimiguel said:
hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...
Click to expand...
Click to collapse
Yes, I suspected as much, this is a known bug. I will keep working on it.

delete my thread immediately thank you ........

[ROM][DISCONTINUED][9] LineageOS 16.0 [I9515][I9515L]

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: 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 Galaxy S4 Value Edition over 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: Will jfvelte ever receive official builds from LineageOS?
A: YES! The first official Pie build was released on 0818!
Q: How often will new builds be released?
A: There will be no further unofficial builds on a regular basis, only whenever a new feature or bug fix is being tested. Please discuss all future unofficial builds with me via pm or on Telegram.
ROMs
ripee
- GT-I9515/L: jfvelte
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
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 LineageOS 16.0!
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.
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
- You tell me!
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
- arco68, npjohnson, and every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for jfvelte.
Sources
- android_device_samsung_jf-common
- android_device_samsung_jfvelte
- android_kernel_samsung_jf
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy S4
Contributors
ripee, Exodusnick, PixelBoot, sonic_sakthivel123, chingoboy, Roberto.caramia, sombree
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Stock KitKat for your variant.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-17
Created 2019-07-13
Last Updated 2019-08-17

Reserved
Mod Edit:. Development must be primarily accomplished via Xda. TG group traffic not permitted without any development on Xda.
OP Edit: Sources updated.

Reserved

I'm using this ROM since one month and I can say that is the smoothest I ever run on my phone.
So I would say thank you to @ripee for his hard work and to let me being part of the testing.

Thanks to @ripee , my phone is back from its dead!

* * * Thread Cleaned * * *
Let's keep the comments related to development of this Rom, not snarky, disguised attacks on other members.
If you believe someone has violated Forum Rules, simply REPORT the comment. Making your argument in the development thread is not only prohibited, it shows poor character and clutters Xda with useless rubbish.
This will be the only courtesy warning those involved will receive.
Please, follow the rules when posting, and take the appropriate course of action to report any violations.
Thanks for your cooperation.

Changelog
Build 0716
* BT calling is fixed!
* Synced with LineageOS sources.

app startup option
I can't find the app stop option at startup as lineage os 14.1

Diabolik2770 said:
I can't find the app stop option at startup as lineage os 14.1
Click to expand...
Click to collapse
I don't fully understand what you mean. I don't remember if this was a feature in 14.1, but if it was, it has been removed in 16.0.
If you want to disable an app so that it's hidden, you have to do it in its settings. You have to do this for every app you want to hide.

How is the battery drain and the speed on this ROM? Stability?
I have not changed the ROM on this phone for a very long time!
Currently I am still using CM13, which (except for a sometimes rather buggy camera access) works pretty well. The battery drain and speed is not perfect, but who expects this on a phone this old. It is enough to use it daily without pain.
But I can already say thank you very much for this ROM and for keeping this device alive. I am really suriprised to see a rather uncommon device still supported after so many years.

5g BUG
Wifi 5G signal is too weak, can't stay connected for long...

Changelog
Build 0810
* Sources changed to official jfvelte and jf-common repos: one step closer to official support!
* Synced with LineageOS sources.
In order to build your own, use this roomservice:
Code:
. build/envsetup.sh
repopick -f 250250 253025
brunch jfvelte

bootloop in i9515L
I am installing the rom correctly but I get a message "Set Warranty Bit: Kernel" and it is in boot loop does anyone know how to solve?

"Set Warranty Bit: Kernel"
is normal .
The first boot process can take up to 10 minutes.

Exodusnick said:
"Set Warranty Bit: Kernel"
is normal .
The first boot process can take up to 10 minutes.
Click to expand...
Click to collapse
I think I wrote it wrong sorry for the English. After the screen written "GALAXY S4 I9515L" the screen goes black and restarts, should I wait then?

@WevsSW
S4 I9515L I can't say anything because I don't own the device, sorry
but normally it should work on the device, too.

Strange that only lineage 15 and 16 don't work for me. All the other custom roms I tested worked, including lineage 14.1... Even so, thank you very much and sorry for the inconvenience

Its over 36hrs+ that I installed this rom & I didnt have any issue, its amazing and thanks to everyone who is making this happen.
Diabolik2770 said:
I can't find the app stop option at startup as lineage os 14.1
Click to expand...
Click to collapse
You need to enable Developer options by going to Settings > About phone > scroll to the end and tap 7 or so times on Build number.
Then go back to Settings > System > Advanced > Developer options > Memory > Apps started on boot...
Then you can enable and disable for each individual apps including other permissions.

Respect and appreciate your efforts @ripee for making ROM for this device on Pie:good::victory:
Using your 1st build since a week and the device works without issues. Battery is definitely better than Oreo.
Thanks for release!

adammanson said:
Its over 36hrs+ that I installed this rom & I didnt have any issue, its amazing and thanks to everyone who is making this happen.
You need to enable Developer options by going to Settings > About phone > scroll to the end and tap 7 or so times on Build number.
Then go back to Settings > System > Advanced > Developer options > Memory > Apps started on boot...
Then you can enable and disable for each individual apps including other permissions.
Click to expand...
Click to collapse
found
Thank You !!

[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]

I was just curious about GApps for this ROM. Going to the link you provided and just simply going to opengapps.org/ does not show a gapps version for Android 10. Is it ok to use one for Android 9?
EDIT: I was searching around for a GApps package for Android 10 and found this.... https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
I installed your ROM with the GApps above and it is working great so far. Thank you for the work you put in making this for all of Nexus 7 owners!

Is LineageOS seperated from AospExtended in the other thread?
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
Viking8 said:
I was just curious about GApps for this ROM. Going to the link you provided and just simply going to opengapps.org/ does not show a gapps version for Android 10. Is it ok to use one for Android 9?
EDIT: I was searching around for a GApps package for Android 10 and found this.... https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
I installed your ROM with the GApps above and it is working great so far. Thank you for the work you put in making this for all of Nexus 7 owners!
Click to expand...
Click to collapse
Use the latest beta, some bugs were fixed.
https://sourceforge.net/projects/opengapps/files/arm/beta/20200116/

edison0354 said:
Is LineageOS seperated from AospExtended in the other thread?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=81555475&postcount=2938
Lineage-17.1
Like mentioned before .. I did plan to handover Lineage-17.1 beginning of 2020.
That's done now.
@ripee will continue to build regular lineage-17.1 builds for flo/deb.
If there are some code changes in the next time .. we test on AEX first and apply changes to Lineage sources later on.
Thanks to @ripee for taking over !
Cheers

Nice job

I would like to use microG with this ROM. Any chance to include signature spoofing into the ROM? Or do you know of any other method to use microG with this ROM?

Changelog
Build 0122 for both variants
* NFC is fixed, courtesy of followmsi.
* Synced with LineageOS sources.

Thanks ripee for the quick update!
But for flo, I still see the 21 version?!?

rho-bot said:
Thanks ripee for the quick update!
But for flo, I still see the 21 version?!?
Click to expand...
Click to collapse
I post changelogs while the builds are still cooking or uploading, in case I forget to do so later.
flo 0122 is up right now.

Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?

Vincent_40 said:
Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?
Click to expand...
Click to collapse
I am also curious. My USB port is not functional so I need to always keep one or two OS zip files on internal storage.

1st post tell us that we need a repartition to have enough space to install gapps. During this step /data partition is erased.
---------- Post added at 11:24 PM ---------- Previous post was at 11:00 PM ----------
WackyDoo said:
I am also curious. My USB port is not functional so I need to always keep one or two OS zip files on internal storage.
Click to expand...
Click to collapse
It's time to try to fix that USB port !
I've done it twice. The first time I tightened the ground contour with a small pair of pliers. The 2nd time I managed to redo the soldering with a sharp soldering iron.

Vincent_40 said:
Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?
Click to expand...
Click to collapse
No, only wipe system, cache, dalvik, and data.

ripee said:
Changelog
Build 0122 for both variants
* NFC is fixed, courtesy of followmsi.
* Synced with LineageOS sources.
Click to expand...
Click to collapse
Cool downloading now does substratum work with this ROM though?

having a lot of trouble installing. I am not sure if it is user error. crying
when can we have ota?

Flo clean flash from 01/09 version w/beta gapps pico 01/16 & latest magisk.
No issues, nice easy upgrade. Looking forward to dirty flashing going forward.
Many thanks to both maintainers! Appreciate the option of latest roms on our devices.

I haven't tested yet with LOS17.1, but new Open GApps are working with Setup Wizard on Havoc. I'm using Pico.
https://www.xda-developers.com/open-gapps-android-10-roms/
Edit: Tried it on LOS17.1 and it's working great!

Thanks for this ROM.
Works fine on that old device ?.
Do you think it's possible to implement smart charging feature ?

Another happy user here, i even mamaged to load credits to my public transport card via NFC.

dealpapa1 said:
having a lot of trouble installing. I am not sure if it is user error. crying
when can we have ota?
Click to expand...
Click to collapse
I'm sorry to hear that. Which part of the installation process are you stuck on?

Development [ROM] [12.1] [OFFICIAL] Android Ice Cold Project

{
"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-S 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 17.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:
NikGapps Core is recommended
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
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 how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: 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.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, 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 S. 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 (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
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 A/B 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.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP 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.
Open the updater app, download the update, then press install, press reboot when prompted, you will be taken to TWRP, there isn't any need to flash GApps separately
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
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:
GitHub - AICP/kernel_xiaomi_vayu
Contribute to AICP/kernel_xiaomi_vayu development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_xiaomi_vayu
Contribute to AICP/device_xiaomi_vayu development by creating an account on GitHub.
github.com
Vendor source:
Follow this guide if you want to extract the vendor blobs
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:
@kubersharma001
@nullxception
@SebaUbuntu
Information:
ROM OS Version: 12.1
Kernel: Linux 4.14
ROM {Firmware|Vendor} required: 13.0.2
Status: STABLE
You want to see a "normal" night at the "DEV office", click here!!

Wow. Thank you @Nebrassy . I am a long time lover of AICP and it is wonderful to see it for this device. Your hard work is much appreciated and I am happy to donate to the cause: Transaction ID 3HG14334YS520444K.

Thank you dev for your work!!
Can you please tell me: the "Xiaomi parts" shown in the screenshots provided in the Telegram channel, where can I find them?
Or is this something that will be implemented later on?
Thanks!!

juv3nal said:
Thank you dev for your work!!
Can you please tell me: the "Xiaomi parts" shown in the screenshots provided in the Telegram channel, where can I find them?
Or is this something that will be implemented later on?
Thanks!!
Click to expand...
Click to collapse
We don't currently have that, and I didn't provide any screenshots

Thanks, this one is an old favorite of mine

Thank you .

Any solution to root and keep using my banks apps and some games like pokemon go?
Thanks for this ROM .. extremely fast and solid ROM.. just one little thing that I found is that notification sounds not always works it only vibrates

julioolares said:
Any solution to root and keep using my banks apps and some games like pokemon go?
Thanks for this ROM .. extremely fast and solid ROM.. just one little thing that I found is that notification sounds not always works it only vibrates
Click to expand...
Click to collapse
SafetyNet passes by default with or without magisk, not sure how you're having problems with that

Nebrassy said:
SafetyNet passes by default with or without magisk, not sure how you're having problems with that
Click to expand...
Click to collapse
How to safetynet pass? I've just rooted my device but seems like safetynet it's missed
EDIT: FIXED.

Does anyone else have issues with receiving timely notifications and not being able to receive text messages?

AusVGM said:
Does anyone else have issues with receiving timely notifications and not being able to receive text messages?
Click to expand...
Click to collapse
Nope, everything here is working good at my side, these bugs sometimes the gapps package might be its cause, try a different gapps package, this would solve your latency.

AbboodSY said:
Nope, everything here is working good at my side, these bugs sometimes the gapps package might be its cause, try a different gapps package, this would solve your latency.
Click to expand...
Click to collapse
Swapped from MindTheGapps to NikGapps and the problem has been solved. Thank you very much.

I switched from Pixel Plus UI to AICP and I must say that AICP is just as fast and smooth which is impressive considering how much tweaks and customization features are baked into the ROM.
There is only one small issue. I have observed some gallery lag in this ROM that didn't exist in MIUI or other ROMS. Namely, when I open any gallery app, it takes a few seconds to actually load the images. Has anyone else noticed this or is it an isolated event?
For consideration I am using the recommended mind the Gapps.

yonoshiro said:
I switched from Pixel Plus UI to AICP and I must say that AICP is just as fast and smooth which is impressive considering how much tweaks and customization features are baked into the ROM.
There is only one small issue. I have observed some gallery lag in this ROM that didn't exist in MIUI or other ROMS. Namely, when I open any gallery app, it takes a few seconds to actually load the images. Has anyone else noticed this or is it an isolated event?
For consideration I am using the recommended mind the Gapps.
Click to expand...
Click to collapse
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.

AbboodSY said:
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.
Click to expand...
Click to collapse
Coincidentally, I am also using simple gallery pro. I will try switching Gapps and I will report back. Thank you for taking the time to assist me.

AbboodSY said:
To be honest I'm not facing this issue..
I'm using simple gallery pro and the images are loaded pretty fast so.. I advise you to flash NikGapps, as MineTheGapps is really causing alot of bugs recently.
Click to expand...
Click to collapse
Okay. Very odd. I still had the issue with NikGapps. Then I saw AICP had an update (Thank you Dev) which I did OTA. The issue persisted. I then decided to go for broke and just do a complete wipe and clean install of the latest AICP Rom and Mindthegapps and the issue is resolved. Could have just been an issue with my initial installation.

Loving the latest update @Nebrassy . This ROM is rocking my world! I have made another small donation towards your good work. Thank you for your efforts. They are much appreciated.
Transaction ID: 6RV661328U952290X

FlameGapps is now the recommended package for vayu

Hi, recording on the stock camera show garbage, and tried installing a gcam and still same. It like dthis.
I tried fresh clean install of rom and flashed flameGapps
clean cache/data same.

pinbanman said:
Hi, recording on the stock camera show garbage, and tried installing a gcam and still same. It like dthis.
I tried fresh clean install of rom and flashed flameGapps
clean cache/data same.
View attachment 5413861
Click to expand...
Click to collapse
Use latest build, 17th of September

[Discontinued][ARM64][ROM][11.0][OFFICAL] AICP 16.1 [Addison]

{
"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)
Camera mods are not and will not be supported
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 (TWRP recommended).
3. Wipe the System, 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, enable developer settings and in them, OEM unlock/Advanced reboot/USB tethering.
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 TWRP 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:
GitHub - AICP/kernel_motorola_msm8953 at r11.1-albus
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
Device tree source:
https://github.com/AICP/device_motorola_addison/tree/r11.1Vendor source:
Follow this guide if you want to extract the vendor blobs
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:
erfanoabdi, npjohnson, jeferson1979, jarlpenguin,alberto97
Information:
ROM OS Version: 11.x
Kernel: Linux 3.18.140
ROM Firmware required: ADDISON_OPNS27.76
Status: STABLE
Release Date: 19-12-2021
You want to see a "normal" night at the "DEV office", click here!!

19-12-2021: Initial release

solved, ask me for unlock code...
i forget format data....
Thx
Running on android 11 Now!!!
Thx!!!!!!

Thanks for the oficial release. Working fastest.
Running in XT 1635-02 with Nano Gapps
Greeting from Brazil

Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.

Good customizations and performance. Free ram at 800-1300mb. Screens of the ROM:

BloodyPorra said:
Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.
Click to expand...
Click to collapse
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help

marcost22 said:
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help
Click to expand...
Click to collapse
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:

BloodyPorra said:
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:
Click to expand...
Click to collapse
I can see some things that might cause that audio issue; altho it's weird that i cant notice it; it might just be the opalum speaker protection being all wonky.
You are gonna have to get me a console-ramoops from after the reboot, just pull /sys/fs/pstore, because those have no info for me
I even have a XT1635-02 myself as my test device, the only thing different is that i have an ever so slightly newer firmware version; M8953_10238.63.04.83R vs M8953_10238.63.04.83.01R on mine

Sound is low and fixed and back again very loud with noise, distortion and popping. After notification in whatsapp. Ok i want to check this.
(Edit):
console-ramoops isn't available after kernel panic

Here for you

BloodyPorra said:
Here for you
Click to expand...
Click to collapse
nothing, you might have to take the logcat with a pc and then trigger the flashlight to see if the issue pops up

marcost22 said:
nothing, you might have to take the logcat with a pc and then trigger the flashlight to see if the issue pops up
Click to expand...
Click to collapse
CPU Shutdown if i shake my device for flashlight or not. How to take a logcat with my notebook?

I take the logcat in ADB after shake several times my device is shutdown again, but only the last line appears:
Code:
12-21 10:21:44.628 0 0 I : [ 1520.174098,4] motosh 4-0043: Sending disp_rotate(x)value: 0

you start adb logcat -b all > log.log and then after a couple of seconds you shake the device

marcost22 said:
you start adb logcat -b all > log.log and then after a couple of seconds you shake the device
Click to expand...
Click to collapse
after several times shutdown

Thanks for your hard work dude

BloodyPorra said:
after several times shutdown
Click to expand...
Click to collapse
can't see anything wrong at first glance; will take a better look tomorrow

rogerpinkos said:
Thanks for your hard work dude
Click to expand...
Click to collapse
in my device i tested games like a Mobile Legends and COD i have a fastest perfomance, system is fluid and lag free. big different when i using arm or arm64 pie roms

marcost22 said:
can't see anything wrong at first glance; will take a better look tomorrow
Click to expand...
Click to collapse
i was to test dolby atmos or viper for sound fix and change CPU governor and I/O for tests.

Database Info

welcome