[ROM][9][Pie][Flo][Deb][UNOFFICIAL] ViperOS v6.7 for Nexus 7 2013 (11/20/2019) - Nexus 7 (2013) Android Development

{
"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"
}
This is ViperOS
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
"This is a user friendly thread. All feature requests will be heard and considered. I am not against anything that doesn't stray too far away from the original idea of the ROM! Helping one another is also encouraged! Please be respectful and you will always be treated the same way, we are all here for a good experience."
About:
We are a Brazilian team, ViperOS aims to bring stability and useful features. If you are looking for a stable ROM with true tested features, minimal bugs and no Lineage bloatwares, then this is the place to be.
Features:
Statusbar
QS settings
Clock statusbar settings
Battery style
Carrier label
Network traffic
VoLTE icon toggle
4G/LTE icon toggle
Rounded corner settings
QS for Reboot/Recovery
QS Screenshot full and partial
Recents
Style recents AOSP and QuickStep
Button clear and Membar for recents AOSP
Lockscreen
Face auto unlock
Fingerprint authentication vibration
WeatherClient
Battery info Charging
Ambient music ticker
System
Color engine
Theme QS style
Styles switch
Styles clock lockscreen
Buttons and navbar settings
LED battery charging
LED notifications colors
Power Menu advanced
Fonts packages
Pulse Navbar
VPapers
Many other customizations, install and take a look
Known issues:
- NFC has been enabled and is working but i recommend turning it off to prevent excessive batttery drain
- Navigation bar glitches sometimes.
- 1.3gb system partition is required to be able to flash this ROM.
- You tell us!
Installation:
1. Download either latest ViperOS v6.7 for flo or ViperOS v6.5 for deb, and Latest OpenGapps and Magisk if you want root from the links below.
2. Wipe everything except internal storage.
3. Flash the ROM from the links below.
4. Flash the ViperOS v6.7 Universal ROM Fix if you flashed the flo v6.7 ROM version to get a fully working viperos build (YOU NEED THIS IF YOU HAVE FLO) from the links below.
5. Flash either latest Opengapps package or ViperGapps package from the the links below.
6. Flash Latest Magisk from the links below.
7. Reboot and Enjoy!
Download:
Flo v6.7 11/20 is here: https://www.androidfilehost.com/?fid=4349826312261637095
Flo v6.7 11/20 Extra Apps build is here: https://www.androidfilehost.com/?fid=4349826312261637127
Flo v6.7 11/20 Univeral ROM fix is here: https://www.androidfilehost.com/?fid=4349826312261639553
Deb v6.5 6/19 is here: https://www.androidfilehost.com/?fid=6006931924117921945
Flo/Deb Download folder is here: https://www.androidfilehost.com/?w=files&flid=294807
ViperGapps download: https://sourceforge.net/projects/viper-project/files/ViperGApps/
OpenGapps download: https://opengapps.org/
Magisk: https://github.com/topjohnwu/Magisk/releases
Sources:
Deb Device Tree: https://github.com/deb-flo/android_device_asus_deb/tree/viper-pie
Flo Device Tree: https://github.com/deb-flo/android_device_asus_flo/tree/viper-pie
Kernel: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-pie
Vendor: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-16.0

reserved for future use
Flo and Deb builds are up!
Huge thanks to @ripee for helping me build this ROM

Some screenshots

New Build has been uploaded today for flo! It's ViperOS v6.5 with june security patches!
Download here: https://www.androidfilehost.com/?fid=6006931924117899502

Will there be an updated version for deb too? I get an error7 trying to install the last version.

mykey2 said:
Will there be an updated version for deb too? I get an error7 trying to install the last version.
Click to expand...
Click to collapse
I got the same error on my Deb fwiw.

slapshot2286 said:
I got the same error on my Deb fwiw.
Click to expand...
Click to collapse
Usually it happens with TWRP older than 3.2. Simply flash the linked below version 3.3.1, reboot back into recovery, and flash the rom zip again.
TWRP - Asus Nexus 7 2013 LTE (deb)
TWRP - Asus Nexus 7 2013 Wi-Fi (flo)
Hope it helps.

I LOADED TWRP 3.3.1 I am still getting the ERROR: 7 error, I even went as far as removing the "assert" line from the installer with the same result.
Any other ideas?
===
Additional information from the recovery file:
Code:
Patching system image unconditionally...blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/5a79362318d00cf4c316e86435b3ed38dd35082d/
565739520 bytes free on /cache (0 needed)
[B]/cache/recovery/last_command doesn't exist.[/B]
erasing 93037 blocks
[B]BLKDISCARD ioctl failed: Invalid argument[/B]
failed to execute command [erase 6,788,4689,236238,294400,295426,326400]
new data receiver is still available after executing all commands.
[B]script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 19 second(s).[/B]
Error installing zip file '/sdcard/Viper-flo-20190619-v6.5-UNOFFICIAL.zip'
Updating partition details...
I:App found at '/system/priv-app/twrpapp'
I:Data backup size is 3465MB, free: 3136MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Piosio said:
Usually it happens with TWRP older than 3.2. Simply flash the linked below version 3.3.1, reboot back into recovery, and flash the rom zip again.
TWRP - Asus Nexus 7 2013 LTE (deb)
TWRP - Asus Nexus 7 2013 Wi-Fi (flo)
Hope it helps.
Click to expand...
Click to collapse

Piosio said:
Usually it happens with TWRP older than 3.2. Simply flash the linked below version 3.3.1, reboot back into recovery, and flash the rom zip again.
TWRP - Asus Nexus 7 2013 LTE (deb)
TWRP - Asus Nexus 7 2013 Wi-Fi (flo)
Hope it helps.
Click to expand...
Click to collapse
Yup I've been on 3.3 for a while. No luck.

There is an issue with the installer script, I am trying to track it down. I tried Lineage 16 with no issues..
I did note that if you try to install or reinstall the ROM you MUST reboot into recovery to make it work, I will be testing Viper once I get Lineage set and backed up..
Update
I tried the updater-script from Lineage same issue, it is beyond my expertise, this ROM looks very nice but no way for me to install as of now..

oldman_58 said:
There is an issue with the installer script, I am trying to track it down. I tried Lineage 16 with no issues..
I did note that if you try to install or reinstall the ROM you MUST reboot into recovery to make it work, I will be testing Viper once I get Lineage set and backed up..
Update
I tried the updater-script from Lineage same issue, it is beyond my expertise, this ROM looks very nice but no way for me to install as of now..
Click to expand...
Click to collapse
Hey guys i forgot that i made a newer viper deb build that i did last month in june and i thought it was uploaded so i deleted the file off my computer to save space but unfortunatly it wasnt uploaded so i apologize because i no longer have the ROM file. I am off of work tomorrow so i promise i will try to make a new build for both flo and deb tomorrow. Anyways new viper changes will be included of course as well as july security patches. I have been dealing with some mental health issues the past few weeks and i am a lot better now so i am sorry i haven't been developing lately. Cheers
Edit: i found my missing viper deb build from june i will upload it today at some point

Thank you for all that you do, We look forward to your continued health and if time permits a new release.
Bob
JT1510365 said:
Hey guys i forgot that i made a newer viper deb build that i did last month in june and i thought it was uploaded so i deleted the file off my computer to save space but unfortunatly it wasnt uploaded so i apologize because i no longer have the ROM file. I am off of work tomorrow so i promise i will make a new build for both flo and deb tomorrow. Anyways new viper changes will be included of course as well as july security patches. I have been dealing with some mental health issues the past few weeks and i am a lot better now so i am sorry i haven't been developing lately. Cheers
Click to expand...
Click to collapse

Can anyone help me out with something kinda tricky (even if it's lame)? Let's see...
I have 2 Nexus 7, a 16gb and a 32gb.
Installing ViperOS in both of them (no backup restored) and checking its storage I realized that, in the first one (16gb), system files use 2.8gb and, in the other (32gb), system files use 3.4gb.
Why is there this difference of 600mb between them two? Is it normal?
I'm affraid it has something to do with that repartition issue, that's why I'm asking...
Thanks in advance, guys!

oldman_58 said:
Thank you for all that you do, We look forward to your continued health and if time permits a new release.
Bob
Click to expand...
Click to collapse
Awww.. Your going to make me cry
Thanks so much for your kind words! It means a lot to me
To be truthfully honest with you the past four weeks have been rough for me both physically and mentally. I got so depressed and was having suicidal thoughts. Now I am better though so hopefully we can get this viper issue sorted out

RafaBronX® said:
Can anyone help me out with something kinda tricky (even if it's lame)? Let's see...
I have 2 Nexus 7, a 16gb and a 32gb.
Installing ViperOS in both of them (no backup restored) and checking its storage I realized that, in the first one (16gb), system files use 2.8gb and, in the other (32gb), system files use 3.4gb.
Why is there this difference of 600mb between them two?Is it normal?
I'm affraid it has something to do with that repartition issue, that's why I'm asking...
Thanks in advance, guys!
Click to expand...
Click to collapse
I have no clue I never had or ran into that issue before

mykey2 said:
Will there be an updated version for deb too? I get an error7 trying to install the last version.
Click to expand...
Click to collapse
Yes I will be uploading the latest June deb build sometime tonight or tomorrow
Edit: Okay here it is:
https://www.androidfilehost.com/?fid=6006931924117921945

New build is uploading will update when i can
I am back developing and making roms again

ViperOS 6.7 is having some issues while i was testing the ROM so i found the fix and you will have to flash the fix along with the ROM so i will be making a addon flashable zip fix for ya'll. I will be updating the links hopefully soon

Nice to see you back on the forums JT!!

ianth01 said:
Nice to see you back on the forums JT!!
Click to expand...
Click to collapse
Thanks

Related

[ROM][UNOFFICIAL][UBER 4.9.4][Surnia ][7.1.2 r29] HalogenOS CAF [OMS]

{
"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

[OP3(T)][5.3.X(O)][AOSP] A.O.S.C.P: CypherOS [OFFICIAL]

{
"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"
}
​
This is CypherOS. An extension to the pure Android. Cypher tries to maintain the purity of Android while offering the most useful features to the users. The goal is to give the highest level of performance whilst achieving Simplicity.​
· Ambient Display and Ambient Weather by Chris
· Internal Color Manager by Chris
· Substratum theming engine support (OMS)
· Statusbar - Quick pulldown, Smart pulldown, Network traffic indicators, Statusbar icon customization, Carrier Labels, Clock and Date custimization.
· Quick Settings - QS rows and columns, Wi-Fi easy toggle, Data easy toggle and more
· System - Screenshot types (Fullscreen and Partial area select) and PowerMenu customization
· Notifications - Force expanded notifications, Show notification count, Heads up customization, and Notification LED control.
!!! Flash on your own risk !!!
We will not take any responsibility for bricked devices or lost data. So please watch out!
- Make a (Nandroid) Backup of your current ROM (Recommended)
- Advance WIPE -> wipe /data
- Press install and select the AOSCP rom in sdcard
- Install ROM
- Install Gapps <ARM64-7.1-X>
- After flashing, reboot device (First reboot will take a while)
- Enjoy CypherOS on your device!
-- On dirty flash you need to also dirty flash gapps. The AOSCP survival script deletes them --
[02/02/18]
- Initial release
TeamWinRecoveryProject
Build Status
Official AOSCP Website
My Unofficial Builds Folder
Download Gapps
Temporary Link for Gapps 8.1
For the download of the released ROM always download the latest build
Root with SuperSU | Root with Magisk
Code:
​
Join the Community CypherOS on G+
Join us in Crowdin CypherOS on Crowdin to help us get AOSCP to your language
Join our help Community​
- CypherOS
- LineageOS
- AICP
- PureNexus
- AOKP
- Dirty Unicorns
- and finally me ofc
​
XDA:DevDB Information
[OP3(T)][5.3.X(O)][AOSP] A.O.S.C.P: CypherOS [OFFICIAL], ROM for the OnePlus 3
Contributors
kessaras, steadfasterX, superfes, Sirhc
Source Code: https://github.com/CypherOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: 5.0.1++
Based On: AOSCP
Version Information
Status: Stable
Stable Release Date: 2018-02-02
Created 2018-02-03
Last Updated 2018-03-12
Reserved
>>>>>>>>>> BUG REPORTS <<<<<<<<<<​
We first of all need to think well about it. If its a temperature problem, CPU problem, lag, low fps, display problem, bootloop, infinite boot, or any other problem that anyone would have noticed, but no one reported it, PLEASE think twice before you post it because its impossible to have such a bug and no one noticed it. So something you did wrong. Find it, or clean flash everything from zero.
TWRP, firmware , rom , gapps.
If it's something that propably not many people noticed, then yes take your time, when you have some, and make a nice bug report so i can also see the bug with my eyes and fix it !
Here you will find a very nice guide on how to make a useful log
~ If a stock app crashes or you have an error, i need a logcat and a small explanation on how to re-produce this error to see it with my eyes and fix it.
~ If you come upon a kernel panic , i need a dmesg and kmsg log.
**some more info about the logs: https://forum.xda-developers.com/showpost.php?p=74565097&postcount=94
Please make rensonsible bug reports and don't just come in and report anything that comes on your mind without thinking about it.
The purpose of a bug report is to fix the bug so that we can all enjoy a better rom.
Reserved
Can't wait to give it a try when I get home
kessaras said:
This is the first build. You will find it in the Unofficial folder.
On the next Official Release OP3(T) will be included in the build jobs.
Click to expand...
Click to collapse
Thanks, just flashed on 3T. Looks nice!
Looks like no sound and weird speaker popping instead of music when you try to play any mp3 on device.
SIM card wasn't detected on first boot, second one fixed that.
twoxa said:
Thanks, just flashed on 3T. Looks nice!
Looks like no sound and weird speaker popping instead of music when you try to play any mp3 on device.
SIM card wasn't detected on first boot, second one fixed that.
Click to expand...
Click to collapse
Good. I'm using it already and I'm gonna start debugging everything soon , so I'll get any issue it may have, fixed before the official release date.
deleted
When I last built Cypher, .dataservices stopped working on boot. Can't find any commits that would seem like it would fix that, did you do anything? Or am I just blind lol
*EDIT*
It looks like Chris did a bringup for the op3 again, probably why.
Does this rom replaces recovery? Cause my recovery is replaced and I'm stuck without volte... Can't make calls..
Is there any way i could get root on the recovery that comes with it without the need of pc/laptop?
ZVNexus said:
When I last built Cypher, .dataservices stopped working on boot. Can't find any commits that would seem like it would fix that, did you do anything? Or am I just blind lol
*EDIT*
It looks like Chris did a bringup for the op3 again, probably why.
Click to expand...
Click to collapse
Chris did. Me i was too late to start with it. i came 2nd.
demon507 said:
Does this rom replaces recovery? Cause my recovery is replaced and I'm stuck without volte... Can't make calls..
Is there any way i could get root on the recovery that comes with it without the need of pc/laptop?
Click to expand...
Click to collapse
No it doesn't. Can't flash boot over recovery unless we changed that in "build" which would replace all the people recovery in all roms.
And i don't understand what you are talking about. There is no recovery in it to get root on and generally in recovery mode (TWRP or Cyan) you have root privillages by default. It's impossible in the first place to go into recovery and not have root permissions to flash anything you want...........
kessaras said:
Chris did. Me i was too late to start with it. i came 2nd.
No it doesn't. Can't flash boot over recovery unless we changed that in "build" which would replace all the people recovery in all roms.
And i don't understand what you are talking about. There is no recovery in it to get root on and generally in recovery mode (TWRP or Cyan) you have root privillages by default. It's impossible in the first place to go into recovery and not have root permissions to flash anything you want...........
Click to expand...
Click to collapse
I flashed this rom over oos...now my recovery is not twrp...it says something like android recovery...i don't even recognize which recovery is that...anyways... I'll flash twrp once i get home after 4days...untill then no calls..
demon507 said:
I flashed this rom over oos...now my recovery is not twrp...it says something like android recovery...i don't even recognize which recovery is that...anyways... I'll flash twrp once i get home after 4days...untill then no calls..
Click to expand...
Click to collapse
Did u just say you flashed a custom ROM over Oxygen OS?
demon507 said:
I flashed this rom over oos...now my recovery is not twrp...it says something like android recovery...i don't even recognize which recovery is that...anyways... I'll flash twrp once i get home after 4days...untill then no calls..
Click to expand...
Click to collapse
thats called suicide
demon507 said:
I flashed this rom over oos...now my recovery is not twrp...it says something like android recovery...i don't even recognize which recovery is that...anyways... I'll flash twrp once i get home after 4days...untill then no calls..
Click to expand...
Click to collapse
You probably installed outdated twrp, i recommend you install latest Blu.Spark one.
Can you show pictures of this "recovery"?
Also did you really flash rom without wipe cache, system, data??
Why is there second aoscp 5.1 thread?
Ded_Boi said:
Did u just say you flashed a custom ROM over Oxygen OS?
Click to expand...
Click to collapse
I ain't stupid who would flash this over oos without wipe...i meant i flashed this over oos with wipe n all...
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
RKBD said:
You probably installed outdated twrp, i recommend you install latest Blu.Spark one.
Can you show pictures of this "recovery"?
Also did you really flash rom without wipe cache, system, data??
Why is there second aoscp 5.1 thread?
Click to expand...
Click to collapse
I had blu spark twrp before... Anyway I'll fix it soon.
demon507 said:
I ain't stupid who would flash this over oos without wipe...i meant i flashed this over oos with wipe n all...
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I had blu spark twrp before... Anyway I'll fix it soon.
Click to expand...
Click to collapse
if you have root you can install it via flashify
Volte not working for Jio sim
twoxa said:
Thanks, just flashed on 3T. Looks nice!
Looks like no sound and weird speaker popping instead of music when you try to play any mp3 on device.
SIM card wasn't detected on first boot, second one fixed that.
Click to expand...
Click to collapse
Speakers not playing or popping,I've fix that just by running other player,now stock player plays.sim card was detected here,only it lasted few seconds to detect it,I've seen this "bug" before on 7.1.2 ROMs.I flashed Ceasium kernel,and magisk 14.0>15.3,busybox...everything is fine for now.im big fan of Aoscp,Nos and this are my roms of choice.there are also other great roms,there's no doubt,but I prefer this two.thanks to guys who cooked it:thumbup:
Edit:I also see there's 03.02 build made
Sent from my One+3T
Amazing ROM! Everything works just fine! The only difference with the second build I've found is that the screen-off animation is gone, now it is just a fade. Great work by the way!
Sent from my ONEPLUS A3000 using Tapatalk
No network shows on the status bar . And will you add an new function in order to swap the back button and menu ?:silly:

[ROM][9][Pie][Flo][UNOFFICIAL] Pixel Experience Plus (2/13/2020)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience Plus for ASUS Nexus 7 2013 [Flo/Deb]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0 PIE
DON'T FLASH GAPPS, ALREADY INCLUDED IN ROM!​
Installation:
1. Download the ROM and Magisk from the links below.
2. Wipe everything except internal storage.
3. Reboot recovery you will have no OS installed but that's ok i promise your device will boot back into recovery.
4. Flash the ROM and DO NOT flash GApps as it is already included!
5. Flash Latest Magisk to get root access.
6. Reboot and Enjoy!
Known issues:
- You will be required to repartition your device to at least 1.3gb. If you have anything higher or exact than 1.3gb than your fine.
- Navigation bar glitches sometimes.
- Deep Sleep does not work when NFC is enabled so i recommend you disable it when your not using it to get your tablet to go in deep sleep.
- When you boot up the ROM for the first time you may notice that the boot animation will freeze and then your device reboots back to the google logo. This is not a device side issue but a ROM side issue but let the tablet reboot a couple times if necessary & your tablet will eventually boot to the setup wizard and into the ROM. This is normal.
- Use Latest Official TWRP recovery below for Flo which is version 3.3.1.0 and you won't have the install supersu thing when you reboot recovery.
- You tell us!
Downloads:
Latest 2/13 build for Flo is here: https://www.androidfilehost.com/?fid=4349826312261722127
Download folder for Flo is here: https://www.androidfilehost.com/?w=files&flid=293644
Magisk: https://github.com/topjohnwu/Magisk/releases
TWRP: https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img.html
Sources:
Flo Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/pixel-pie
Deb Device Tree: https://github.com/followmsi/android_device_asus_deb/tree/pixel-pie
Kernel: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-pie
Vendor: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-16.0
Thanks dude, I have a LTE version, will you help to release Q for DEB as well? Thanks.
Reserved for future use
one more just in case
Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.
sir_bazz said:
Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.
Click to expand...
Click to collapse
I am using followmsi's latest pixel and pie aosp sources which includes fixes for hardware decoding and compass. I don't have any slow downs when i tested the build however i wouldn't know how to even fix it if there were slow downs because i am just building using his sources. There is nothing changed or added besides those sources. You can expect a new build from me every month with new security patches because i am currently the one mantaining pixel experience
Cheers and have a good day
Is Netflix working on this rom?
guillaumeserton said:
Is Netflix working on this rom?
Click to expand...
Click to collapse
yes but you have to install the older version of netflix look at other peoples posts on different rom threads because i don't care about netflix and you will find the fix there in those threads and posts
Issues
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
The only thing that shouldn't be working is compass and I will hopefully fix it in the next build but gyroscope and accelerometer is working for me on my flo with no problems however I can't say this for deb as I don't have that device to test. But I would do a clean flash wipe everything except internal storage and try flashing the ROM again. Also remember to not flash gapps as its already included
prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.
sir_bazz said:
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.
Click to expand...
Click to collapse
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956
Tested deb for a few days, ( with the patch linked above), and it's pretty good.
Dirty flashed, wiped cache and dalvik, installed ElementalX kernel and then the deep sleep patch.
My early concerns regarding the changed blobs and performance were unfounded. Everything appears to work and the rom runs smoothly.
Did experience an issue with sensors no longer responding after a couple of days and although easily resolved with a reboot, I rolled back to an earlier PE build to avoid a repeat.
Looking forward to trying any further builds though. Hopefully will have time to troubleshoot, or at least a grab a useful log next time.
JT1510365 said:
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956
Click to expand...
Click to collapse
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas
pcmender2005 said:
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas
Click to expand...
Click to collapse
i have no idea it flashes and works fine for me
JT1510365 said:
i have no idea it flashes and works fine for me
Click to expand...
Click to collapse
Ok no probs will have a look at the update script.
I've given this rom a try, and I am also receiving an error 7 from twrp-3.3.0-0-flo
Code:
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,756,4689,298235,326400]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
This device must be re-partitioned before installing this rom
Otherwise works just like it was stated on the original post.
sir_bazz said:
Tested deb for a few days, ( with the patch linked above), and it's pretty good.
installed ElementalX kernel and then the deep sleep patch.
e.
Click to expand...
Click to collapse
which Kernel did you use ? tried both 6 and 7 EX - soft brick
Custom setting
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?
jhford said:
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?
Click to expand...
Click to collapse
Because havoc is more customizable and feature filled compared to pixel experience. Pixel experience is meant to give you the same experience as if you were to use and buy the google pixel phones its the same ROM basically as what the pixel has. There's nothing I can do about this pixel experience is meant to be more of a stock bare minimal experience rom compared to havoc which is more feature filled and customizable.
Cheers
karmacoma7 said:
which Kernel did you use ? tried both 6 and 7 EX - soft brick
Click to expand...
Click to collapse
Apologies man.
Sometimes I completely forget that not everyone here is up to date with development for our devices.
I should've made clear that kernel build is by @followmsi and found in his online file repository.
https://drive.google.com/drive/mobi...k92ZUdnTTg?usp=drive_open&sort=13&direction=a

[ROM][10][Q][Flo][UNOFFICIAL] crDroid 6.0 (12/30/2019)

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!!

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

{
"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 GApps​1. 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 Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps 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?

Categories

Resources