crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Always Have a full functional Backup. Just in case if you want to!
First time installing crDroid to your Nexus 7 2013 or coming from another ROM:
** Make sure you're running a proper working Recovery (TWRP)
1) Copy crDroid zip, gapps zip, to your device
2) Boot into Recovery
3) Wipe everything except internal storage.
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk v20.1 (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
- NFC has been removed and disabled so it's unusable at the moment.
- Navigation bar glitches sometimes.
- Since it's Android Q you may have problems with certain apps not working properly. You will have to tell the developer of the certain app to update their app to be compatible with Android Q. This is not a problem with the ROM.
- Compass seems to not be working.
- Encryption does not work.
- Several crDroid features may or may not be available yet.
- You will be required to repartition your system to at least 1.3gb.
- You tell us!
Downloads:
Latest 12/30 build for Flo is here: https://www.androidfilehost.com/?fid=4349826312261688703
Download folder for Flo is here: https://www.androidfilehost.com/?w=files&flid=302533
GAPPS: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
Sources:
Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/los-17.0
Vendor Tree: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-17.0
Kernel Tree: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-10
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Followmsi (For device, vendor, and kernel sources)
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
Reserved for future use
Happy flashing and enjoy android 10 Q!
I have a problem installing the GApps with ROM build 20191126 . Coming from LineageOS 16.0 (flo) I wiped everything except of the internal storage.
But I always get "Incopatible Android ROM detected. This GApps pkg is for Android 10.0.x ONLY. Please download the correct version for your ROM: 6.0.1 (SDK 23)"
Is this a problem of the ROM or the GApps package?
Frapl
Frapl said:
I have a problem installing the GApps with ROM build 20191126 . Coming from LineageOS 16.0 (flo) I wiped everything except of the internal storage.
But I always get "Incopatible Android ROM detected. This GApps pkg is for Android 10.0.x ONLY. Please download the correct version for your ROM: 6.0.1 (SDK 23)"
Is this a problem of the ROM or the GApps package?
Frapl
Click to expand...
Click to collapse
Have you messed with the build.prop file or any other system files located in system/system in twrp? I did that accidentally and the only way to get it fixed was to reflash the rom and wipe everything except internal storage then reboot recovery then flash the rom and then reboot recovery again and then flash gapps. Try that and make sure you have the latest version of twrp recovery
Hi all.
Just downloaded crDroid to give a test spin to see how it is.
I'm primarily a gzr, aex guy.
LineageOS and crDroid are my next rom choices.
A note about OpenGapps 10.
It has issues mounting system on some devices.
Installing ROM, rebooting into system and then rebooting back into recovery, works.
Honestly takes too long for me.
A quicker way that normally works is.
- Install ROM.
- Mount (or unmount and remount) system in TWRP.
- Install OpenGapps 10.
- Reboot to system.
- - or install Magisk, kernel, what ever else and then reboot to system.
At first glance, crDroid seems to be working well. :highfive:
Cheers.
Thanks for the suggestion to Mount the system in TWRP. That fixed my issue.
JT1510365 said:
Have you messed with the build.prop file or any other system files located in system/system in twrp? I did that accidentally and the only way to get it fixed was to reflash the rom and wipe everything except internal storage then reboot recovery then flash the rom and then reboot recovery again and then flash gapps. Try that and make sure you have the latest version of twrp recovery
Click to expand...
Click to collapse
I did not modify anything, just coming from LineageOS 16.0 (by ripee) wiped everything, except the internal storage, and installed your rom using TWRP-3.3.1-1_UA. My current solution is to modify the GApps package install script so the version check is not failing. At the moment everything is running fine.
Frapl
Thank you @JT1510365 for giving Flo another Android 10 ROM.
Coming from @followmsi aex 7 Aplha.
I see you mentioned 1.5Gb required for system, but I have partitioned with @followmsi 1280_120 script. After reading a post by Clamor about partitions to 1.5Gb required complete format look complex. I skipped the process.
I'm able to clean flash your ROM, with OpenGapps beta Pico (unmount-remount system in TRWP, with @ipdev suggestion).
Run really smoothly so far, but I did encounter 2 problem.
1) video glitch, a fix was given by @ipdev to mod media_codecs.xml (see attached screenshot)
2) when tap battery in settings, it crashed. Return to home screen.
Thanks again!
Update to 2.
After pressed battery in settings, crashed back to home screen. A small window appeared, I select app info and settings info appear. Did the clear cache, no go. Clear cache and storage (Bad idea) and reboot. After the cdroid bootanimation, screen just faded to Black. No lock screen, not able get back into ROM.
Did a complete clean install of ROM only, reboot into ROM. No other things are added, tapping battery in settings still crashed. Is no biggy, does not take away the smoothness of the ROM.
Anyone know how to get weather next to the home screen at a glance?
This is such a fantastic ROM. Thank you so much JT1510365!
No hassle clean install, extremely solid & dependable, and now the daily driver on the FLO.
I do very much wish that it was available for the DEBs.
blambo said:
This is such a fantastic ROM. Thank you so much JT1510365!
No hassle clean install, extremely solid & dependable, and now the daily driver on the FLO.
I do very much wish that it was available for the DEBs.
Click to expand...
Click to collapse
wish granted will try making a deb build tonight
Thank you for your kind words
Happy New year @JT1510365! ?
All the best to you in 2020!
Thanks for creating ROM for all of us, really appreciates your time! ?
JT1510365 said:
wish granted will try making a deb build tonight
Thank you for your kind words
Click to expand...
Click to collapse
Your work, help, and support are very much appreciated JT1510365. Please just take it slow and have fun with it.
Let me know if I can be of help in any way.
And, have a happy, healthy & prosperous New Year!
blambo said:
Your work, help, and support are very much appreciated JT1510365. Please just take it slow and have fun with it.
Let me know if I can be of help in any way.
And, have a happy, healthy & prosperous New Year!
Click to expand...
Click to collapse
Thank you and I will let you know when the deb build is available
Anyone having issues with camera on this build?
JT1510365 said:
Anyone having issues with camera on this build?
Click to expand...
Click to collapse
Camera (still picture and video recording) are working fine for me.
JT1510365 said:
Thank you and I will let you know when the deb build is available
Click to expand...
Click to collapse
I peeked into your crDroid 10 DEB upload folder and found it.
You have done it!
Wipe everything but internal, install crDroid 10 DEB, install open_gapps-arm-10.0-nano-20190928-BETA, install Magisk 20.03. Wipe caches.
Very fast first boot time. No hiccups.
Quick page to page crD setup.
Set smallest width to 703.
Playstore/Google account login no issues.
Backup+ restore no issues.
Magisk SafetyNet Check: Success. No issues.
Good battery life & charge time, no issues.
Screen rotation no issues.
Camera fine no issues.
Networking & VPN Hotspot no issues.
LTE signal XLNT!
So far, this puppy is solid as a rock. Everything that I use it for works. (Wireguard, VPN Hotspot, Netflix, Plex, MXPlayer Pro HW+, email & web browsing, Juice SSH, AdminHands, etc.) No crashes/FCs/errors so far.
A great many thanks to you for your work, and for breathing new life into these DEB & FLO JT1510365! -Android 10 for DEB is a unique challenge, and very much appreciated.
Magnificent!
Is there any custom Kernels that work with 10 roms?
twist3d0n3 said:
Is there any custom Kernels that work with 10 roms?
Click to expand...
Click to collapse
No, sorry
Thanks!
hey how did you got netflix running? cant here. thx!!
Related
{
"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"
}
Android, Reimagined.
For the best experience, view the thread on a web browser like Chromium or Firefox.
Desktop: Brilliant. Mobile: Good. Tapatalk: OK. XDA-Labs: Horrible.
Code:
YOU are doing modifications to your device.
YOU are responsible for what you do.
We are not responsible for any damages, data loss or any type of unexpected,
bad or damaging results! If you have SERIOUS problems with this software,
please contact the developers or maintainers. We are not liable for anything
bad that happens to your device.
As long as you are responsible, some companies such as OnePlus
WILL HONOR IT. Some people occasionally describe them as heroes.
Don't be stupid and bet on that though, please be responsible for what you do.
We prohibit you from overclocking to 1337 GHz thinking, that an OEM would
replace your glorious space heater etc.
We recommend you to take the advice above regardless.
halogenOS Checklist
Although no data should be lost or damaged by the flashing process,
we advise you to follow the following steps if you are coming from another rom:
Please take a full nandroid backup!
Please copy your back up to an external device.
Backing up your Internal Storage is also recommended.
When completed, please clean flash the build!
XOS is a new generation cutting-edge OS for Android based on Code Aurora Forum releases.
What is XOS?
halogenOS, also known as XOS is a new Android ROM which ships with the global aim to
become a modular ROM which keeps as high as potentially possible operating
performance on your mobile device while still maintaining a sufficient feature
base of nice, small and minimal features that would not be available via any
external feature base, extension, mod or plugin.
We hope you have a truly halogenified experience!
Internals of XOS
At core, the ROM is composed mainly of components from CodeAuroraForums (CAF),
featuring only extremely minor set of components from CyanogenMod (CM) which
have been added to source in order to allow for better cross-device compatibility.
Our LOVE to others
A huge thanks goes to those behind the CodeAuroraForums (CAF), the CyanogenMod
organization and all of its
contributors for the sources used in the development of the base ROM which we
started with inclusive of all the work and dedication their team puts in order to
keep us updated on the awesome contributions that they make.
We will be keen on ensuring that we be up to date with the code from our base sources,
with regular ROM updates hopefully coming from time to time.
Please do not ask for ETA's (else you shall be spooked by Mr Skeltal). Almost all of us are
students, and with the current lifestyles and routines we have, it is not that easy to acquire
time to develop the ROM, though we'll be sure to keep you updated and release OTAs as
soon as they are available and ready for publication. If you want to be really updated quick,
then join us on Telegram: http://telegram.me/halogenos
Visit our website for features such as: Downloads, Information etc.
http://halogenos.org
(Not finished yet)
Common stuff
The ROM is super stable as of now and we'll maintain a clean and proper ROM.
Known issues are going to be fixed as soon as possible. We don't have infinite time.
Highlights :
Substratum
Full media support (FFMPEG, video codecs, ...)
Great Audio quality, no distortions, no crap
Optimized many portions of the system including surfaceflinger, inputflinger, System Server, and more
Super fast boot
Superuser-capable
Great battery life
Soundmod support (not all soundmods work on Nougat, it's not our fault)
addon.d support (backups your gapps etc. when flashing new build - don't wipe system before flashing!)
init.d support
BusyBox
Disabled Access Time for all partitions (We don't need access time. When access time is enabled, it will store the exact date of the access when a file is accessed, what just wastes write cycles (in theory) and has impact in I/O performance.)
Super smooth
Signature Spoofing toggle (Support for MicroG)
Support for trusted third-party WebViews like Chrome
Long press on home for assist toggle
Security Patches in kernel
OpenGapps (Mini/Micro/Nano recommended) and Banks GApps support
Full KeyHandler & KeyDisabler support
Dexpreopt for faster (first) boot time and less space consumption on data partition
Upgrade & Boot the ROM in just 5 minutes - no more endless waiting for flashing a new build
Very high compatibility with other ROMs
How to update the ROM:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Do not wipe anything
Flash the ROM
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
You don't need to wipe Cache/Dalvik.
You don't need to flash gapps again. There is some magic going on which keeps your GApps. Just make sure that you don't wipe system before flashing.
You don't need more than 5 minutes.
How to install the ROM for the first time:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Wipe system, data and cache (If you want to try a dirty flash, dont wipe anything)
Flash the ROM
Flash gapps if you want
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema
ROM Download Links
Download halogenOS now
ROM Sources
All sources incl. ROM @ GitHub Organisation
Kernel source-https://github.com/LineageOS/android_kernel_motorola_msm8916
Device source- https://github.com/LineageOS/android_device_motorola_surnia
https://github.com/LineageOS/android_device_motorola_msm8916-common
Vendor source- https://github.com/theMuppets/proprietary_vendor_motorola
Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group
Credits
CodeAurora
CyanogenMod
And everyone else who contributed and helps us!
In case you feel left out here, please contact us!
XDA: DevDB Information
HalogenOS, ROM for the Moto E 2015 Surnia
Contributors
amarc78
Source Code: https://github.com/halogenOS
Change Log: https://github.com/halogenOS/android_vendor_xos/blob/XOS-7.0/Changelog.md
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cm 14.x firmware
Based On: CAF
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-05-24
Created 2017-05-24
Last Updated 2017-08-17
Reserved
Reserved
I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.
amarc78 said:
I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.
Click to expand...
Click to collapse
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.
ENRIQUEMM said:
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.
Click to expand...
Click to collapse
That's strange. I flashed a few builds and didn't have that problem. I'll see what I can do.
I'm running a new build now, the nav bar should be activated on first boot. If so, I'll post it shortly.
Wonderful ROM Works to perfection
RubenPCA said:
Wonderful ROM Works to perfection
Click to expand...
Click to collapse
It does run great. Very quick and smooth.
Sent from my LGLS755 using XDA Labs
Great job
My steps
All wipe
Flash ROM
Flash gapps
Flash supersu
Reboot
Init and freezing then reboot and bootloop
Reflash only ROM and gapps
Run
This ROM is fantástic
Just an observation, try to install it from the official twrp 3.1.1 and after doing the backup I was unable to access the recovery. Nor restarting in recovery mode even from the fastboot. I had to put back the squid twrp through adb ...
Sorry my bad english
Enviado desde mi XT1524 mediante Tapatalk
Thanks man rom works perfectly ! No issues on first boot!
Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.
ENRIQUEMM said:
Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.
Click to expand...
Click to collapse
I forgot to mention some Bluetooth issues, but I haven't had any trouble staying connected to anything. I thought the only problem was inbound file transfer. I'm working on it. I've been using Magisk without any issues by the way.
After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds
ENRIQUEMM said:
After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds
Click to expand...
Click to collapse
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.
amarc78 said:
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.
Click to expand...
Click to collapse
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you
ENRIQUEMM said:
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you
Click to expand...
Click to collapse
There is an updated SuperSU I see. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
I haven't tested it yet though.
New build is up. Bluetooth should be all fixed now. @ENRIQUEMM I don't have a smart watch to test with if you want to try again and let me know if your problem is fixed.
Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.
801legend said:
Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.
Click to expand...
Click to collapse
Sometimes old Gapps or a bad data connection can make the setupwizard hang. If you weren't using up to date Gapps try updating them. I'f that doesn't work. Try selecting not using any data or WiFi connection on setup. It worked fine for me with 6-17 Open Gapps before I uploaded the build.
Sent from my Motorola XT1526 using XDA Labs
{
"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: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
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: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
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
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- 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
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10
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.
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release
F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above
reserved
I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?
Sweet! I'm gonna be up all night!
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.
Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.
Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it
I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?
So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?
If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix
slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?
{
"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-17.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.3. Simply flash the linked below version 3.3 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: There are no plans to submit these builds for official LineageOS support, but it should not matter. What is most important is that these unofficial builds be stable enough for daily usage, which they are, thanks to followmsi's tireless work in porting Android 10 to these venerable old tablets.
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: Even if neither dev nor flo will ever receive official LineageOS support, just out of curiosity, what are some of the differences be between unofficial and official builds?
A: The following technical changes are in effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Tablet 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.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed, as per followmsi's advice.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
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 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
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 17.1, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-01-21
Created 2020-01-21
Last Updated 2020-04-14
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?
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/Claymore1297/android_kernel_htc_msm8994
Download:
ROM crdroid.net
ViperFX Profile for Speaker
Unzip_me_not_flashabel
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
ViperFX is included and fully suporrted,
just disabel AudioFX or turn on legacy mode.
I dont recommand both together couse (loud bugs)
For those peopel who download over phone i suggest to turn Desktop Mode ON in Browser settings to be abel to Download directly.
Known issues:
Only FM not working, if found something
share log and we will see
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2021-05-11
Last Updated 2021-11-18
Thank you for the great work!
The gapp link is for android 10. Is it good to go on android 11?
Oh, yeah i replaced them. 10 from opengapps not work doe SDK. Nikgapps should work but remember when flash new rom also to flash Nikgapps again , in recovery it will say it will backup and install again but in the end it can lead to bootloop so after a New Build flash Nikgapps again or it will not start. i just looked at Opengapps they dont have 11 there. Or when you want to ungoogel go to /data/app and find vendig or venedig apk and delete it from Recovery in Advanced settings. So it should start without need to flash of Nikgapps
Does not boot for me, even on a clean flash, just reboots with a "TSENS reset" error
Edit : After flashing it like 10 times for whatever reason it booted up just fine, will use it some time and then give you my thoughts
Edit1: After trying to install gapps, the phone crashed on boot with the same error, like 5 reinstalls later, still doesnt work, maybe it could be because my phone is hot, i think TSENS means Temperature SENSor, ill let it cool off a bit.
Edit2: After cooling down the phone shows a different error "KP: EDAC cache: UE instance:cpu7 block L2 'A57 L2 Uncorrectable Error'
This was a very cool rom for the 30 minutes that it worked, i wish i could use it, hopefully you fix these issues.
I wiped everything, installed ROM, but always reboot after logo screen.
firmware 4.16.709.3
twrp 3.4.0.0
Seems very interesting, i tryed before upload and it worked fine by me , but i will now clean flash it and try by my self. I already have the newest build, build and will check these dont forget to thx Claymore to make this possibel
In this rom i have disabled some cores and set some Voltages to enlarge battery and normal performance.
Also i replaced the Camera app to OpenCamera couse this is just a better app for photos and sharpines, also 4k is supported in OpenCamera.
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
tombbb said:
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
Click to expand...
Click to collapse
What youre mean with no luck ?
Was it booting before Gapps ?
@tombbb
platinumthis said:
What youre mean with no luck ?
Click to expand...
Click to collapse
I mean the phone doesn't boot into system, keeping reboot.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
no, I tried only flash Rom, same reboot loop.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
yeah for me too, it did boot one time but after that it never booted again, with gapps or without.
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Click to expand...
Click to collapse
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
tombbb said:
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
Click to expand...
Click to collapse
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
Click to expand...
Click to collapse
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
pinckston said:
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
Click to expand...
Click to collapse
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
tombbb said:
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
Click to expand...
Click to collapse
Did you tried to format /data and then install without gapps ? will this work ?
platinumthis said:
Did you tried to format /data and then install without gapps ? will this work ?
Click to expand...
Click to collapse
I always format data, wipe data,system,cache, install rom, gapp, magisk. But I will try again, maybe flash new build.
What I don't understand is why lineage ROM works?