[ROM] [6.0.1] [MARSHMALLOW] CyanogenMod 13 for Nexus 9 LTE - Nexus 9 Original Android Development

[ROM] [6.0.1] [MARSHMALLOW] CyanogenMod 13 for Nexus 9 LTE - Nexus 9 Original Android Development

About encryption
As you should've already guessed, CyanogenMod 13 will always (re)encrypt your /data partition on first boot unless you flash another kernel with encryption disabled.

Bug reports
Bug reports while using custom kernels, mods (like Xposed) and whatsoever will be ignored.
When reporting a bug don't forget to mention the version you're using (eg.: cm-13.0-20151218-NIGHTLY-flounder_lte), what steps do you need to do to reproduce the problem, what's happening and what it should be happening instead.
Attaching a logcat won't hurt you.

Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk

ss12108 said:
Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Heys!
I don't want to be rude... but:
lcrponte said:
Bug reports
Bug reports while using custom kernels, mods (like Xposed) and whatsoever will be ignored.
When reporting a bug don't forget to mention the version you're using (eg.: cm-13.0-20151218-NIGHTLY-flounder_lte), what steps do you need to do to reproduce the problem, what's happening and what it should be happening instead.
Attaching a logcat won't hurt you.
Click to expand...
Click to collapse
But even that (systemless root), shouldn't justify the issue. logcat would be appreciated.
@lcrponte is using the builtin root access and doesn't have that issue, can you confirm that, if you don't flash chainfire's systemless root, it crashs the same?

sheffzor said:
Heys!
I don't want to be rude... but:
But even that (systemless root), shouldn't justify the issue. logcat would be appreciated.
@lcrponte is using the builtin root access and doesn't have that issue, can you confirm that, if you don't flash chainfire's systemless root, it crashs the same?
Click to expand...
Click to collapse
You aren't being rude. I read the OP...I should have mentioned I did get the bug without systemless root installed. I actually couldn't get root access on anything until I went back into recovery and flashed supersu. As a matter of fact, no logcat apps could gain root to generate a log for the bug, which is why I flashed it in the first place.
If I were able to get a log I would, but without supersu the log apps couldn't get root, and with supersu the log apps just weren't logging anything...at all, not just errors.
Not a big deal to me anyway just figured I'd try to contribute...when I get to work I'll see if I can grab a log from the computer.
Sent from my Nexus 6 using Tapatalk

Let me know if this log helps - https://www.dropbox.com/s/6tkzx629re5uklz/LogCat_Filtered_Error_12-21-2015_13-06.txt?dl=0
I can't revert back from elementalx at the moment because I don't want my data to encrypt...if you need me to I will make a backup and do so later tonight.
Sent from my Nexus 6 using Tapatalk

ss12108 said:
Just one bug I found...using 12-20 nightly and flashed systemless root, arm64 stock gapps. Selecting the "sounds" menu in settings causes an immediate crash of settings. Happens every time. Happened immediately from a fresh, clean flash, and after a reboot, and after a factory reset and reflash. Also happened with elementalx kernel. Tried getting a logcat but I can't get any logcat app to run properly for some reason (might be another bug but could just be me lol).
Everything else seems to work fine for me. Much better than stock so far in my opinion.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This started with 12-19 nightly for me. The 18th build is fine.

briand.mooreg said:
This started with 12-19 nightly for me. The 18th build is fine.
Click to expand...
Click to collapse
Ok good I'm not alone haha.
Sent from my Nexus 6 using Tapatalk

briand.mooreg said:
This started with 12-19 nightly for me. The 18th build is fine.
Click to expand...
Click to collapse
so should we revert to the 18th build? i just installed today as well (latest build) and i'm experiencing the same exact issue.

clamder said:
so should we revert to the 18th build? i just installed today as well (latest build) and i'm experiencing the same exact issue.
Click to expand...
Click to collapse
If sound setup is important to your N9, then I would, I did. Other than the FC though, everything else ran fine.

It's not related to any kind of "root" access. It's a CM-wide bug meaning that you could revert to your last backup or wait for it get fixed.

Flashed 12/24 nightly and the sound settings crash is fixed for me.
Sent from my Nexus 9 using Tapatalk

LTE does not work with CyanogenMod 13 on my device

This is probably a dumb question, but what gapps should I use? The OpenGapps project, which is recommended by Cyanogenmod, does not have 6.0.1 gapps, so I'm kind of lost.

Weird. I tried to use the nano package of that 6.0.X version, but for some reason, I got an error, hence my question.
I'll give it another try, maybe I made some kind of mistake.

thechicgeak said:
LTE does not work with CyanogenMod 13 on my device
Click to expand...
Click to collapse
User problem, not a ROM problem. Flash latest img and repeat the steps on the installation instructions.

imcass said:
Weird. I tried to use the nano package of that 6.0.X version, but for some reason, I got an error, hence my question.
I'll give it another try, maybe I made some kind of mistake.
Click to expand...
Click to collapse
I use the nano, without problems. Make sure you download the 64 bit gapps.

Get rid of corrupted device warning?
Has anyone figured out a way to run this ROM (or any custom ROM) without the nasty "Your device is corrupt ...." (and Santa Claus won't bring you any presents) warning on every boot?
(I feel like this must be an FAQ, but I can't find it in this thread or the CM 12.1 thread, so ...)

ipilcher said:
Has anyone figured out a way to run this ROM (or any custom ROM) without the nasty "Your device is corrupt ...." (and Santa Claus won't bring you any presents) warning on every boot?
(I feel like this must be an FAQ, but I can't find it in this thread or the CM 12.1 thread, so ...)
Click to expand...
Click to collapse
I don't get that message, but I don't know what I did that is different. Elementalx kernel maybe?
Sent from my Nexus 6 using Tapatalk

Related

[ROM][GT-I9190/I9195][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE

{
"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"
}
WARNING! This ROM is for the GT-I9190 and GT-I9195 variant only!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Q/A thread:
N/A
Please use the above unless you have something development-related to contribute here. Thank you.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
CM-12.1 Install Guide
Note: CM for Galaxy S4 Mini is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Download CM-12.1 and gapps-lp zips and put in /sdcard
GT-I9190: http://download.cyanogenmod.org/?device=serrano3gxx&type=nightly
GT-I9195: http://download.cyanogenmod.org/?device=serranoltexx&type=nightly
UPGRADE REQUIRED
Google Apps
Before you install CM-12.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into ClockworkMod recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Install
Use ClockworkMod Recovery.
GT-I9190: http://forum.xda-developers.com/showthread.php?t=2398143
GT-I9195: http://forum.xda-developers.com/showthread.php?t=2364980
Warning: Only use this recovery to flash CM-12.1. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash cm-12*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM-12.1 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM-12.1 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM-12.1 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Useful Links:
BBQLog changelog
serrano3gxx CyanogenMod wiki
serranoltexx CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR NIGHTLY BUILDS!
Source repos:
https://github.com/CyanogenMod/android_device_samsung_serrano3gxx
https://github.com/CyanogenMod/android_device_samsung_serranoltexx
https://github.com/CyanogenMod/android_device_samsung_serrano-common
https://github.com/CyanogenMod/android_device_samsung_msm8930-common
https://github.com/CyanogenMod/android_kernel_samsung_msm8930-common
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/serrano-common
FAQ
Q: How the heck do I get root?
A: Goto Settings and About Phone. Tap Build number 7 times. Go back and enter
Developer options. Change Root access to desired method.
Other Issues?
Use this for obtaining logs.
For nightlies, bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Credits:
Epic Touch CM Team for the install instructions
Everyone that donated beers
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

Reserved

OH YEAH! been waiting like forever! thank you and thanks to everyone is contributing for this device... alright lets get some crashes for my baby just joking

Thank's @arco68 !!! So, what modem do you use? I switched to CNK1 and no more sound problems in calls!!!! Do you think this is modem-related?

96DANGER96 said:
Thank's @arco68 !!! So, what modem do you use? I switched to CNK1 and no more sound problems in calls!!!! Do you think this is modem-related?
Click to expand...
Click to collapse
I'm on CNK1 too, but I've never had any call sound problems though. Some say the issue is caused by the "Ok Google" feature, and that disabling it fixes it.

arco68 said:
I'm on CNK1 too, but I've never had any call sound problems though. Some say the issue is caused by the "Ok Google" feature, and that disabling it fixes it.
Click to expand...
Click to collapse
It is because every thing uses the microphone breaks some thing in The audio routine system, i've tester it personally

Yeah I've given up on trying to figure it out. And no one else in CM wants to help with it, so not much else I can do.

arco68 said:
Yeah I've given up on trying to figure it out. And no one else in CM wants to help with it, so not much else I can do.
Click to expand...
Click to collapse
Maybe you could ask mikereidis (the dev of spiritfm), he has a lot of experience with audio routing issues on a lot of devices
Sent from my GT-I9195 using XDA Free mobile app

arco68 said:
Yeah I've given up on trying to figure it out. And no one else in CM wants to help with it, so not much else I can do.
Click to expand...
Click to collapse
Thank's, nobody answered me on this until now.
And what about battery life?? It is modem related?

96DANGER96 said:
Thank's @arco68 !!! So, what modem do you use? I switched to CNK1 and no more sound problems in calls!!!! Do you think this is modem-related?
Click to expand...
Click to collapse
Have you tried using that fix?
http://forum.cyanogenmod.org/topic/103375-a-quick-fix-for-no-audio-on-calls/

Thanks! Very thanks!

F4k kernel
Is the last f4k kernel (2.2.6) compatible with this official cyano?
However, thank you very much, Arco!

Thanks a lot! Keep the good work!

hey guys, good to know 12.1 is here for us.
quick question, i've been using 12.0, compared to this one, 12.1 is ready for daily use?
thanks!

how are you guys updating your modems and checking the current modems? i'm sure i've done this before and forgotten how/where, as i've got this in my notes:
Code:
AP: I9195XXUCNH5
CP: I9195XXUCNH5
CSC: I9195OJVCNH1
PDA:NH5
PHONE:NH5
CSC:NH1 (XSG)
anyway, flashing 12.1 nightly now, just about to make a build once the repo sync has finished, seems to be stuck on gradle whatever that is, must be big download

sej7278 said:
how are you guys updating your modems and checking the current modems?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/database/GT-I9195/
If I'm in the mood, I download the entire stock ROM and extract the modem. Update via heimdall.

michelsberg said:
http://www.sammobile.com/firmwares/database/GT-I9195/
If I'm in the mood, I download the entire stock ROM and extract the modem. Update via heimdall.
Click to expand...
Click to collapse
being a linux fanboi i'd much rather use heimdall, but downloading an 850mb rom at 15kbps (or whatever these awful hosting sites give) is a pain, although getting kies3 working in a win7 or yosemite vm is more painful it seems.
any instructions how to do it with heimdall, i assume i just install modem.bin or somesuch and don't have to actually flash a whole stock rom/recovery?

Guys, do the changes in today's nightly means cm default kernel is supporting f2fs?

artu72 said:
Is the last f4k kernel (2.2.6) compatible with this official cyano?
However, thank you very much, Arco!
Click to expand...
Click to collapse
Yes, works.
cenovita said:
hey guys, good to know 12.1 is here for us.
quick question, i've been using 12.0, compared to this one, 12.1 is ready for daily use?
thanks!
Click to expand...
Click to collapse
It seems to be pretty stable. Faced no FCs or Bugs until now, so I'd say yes.

sej7278 said:
being a linux fanboi i'd much rather use heimdall, but downloading an 850mb rom at 15kbps (or whatever these awful hosting sites give) is a pain, although getting kies3 working in a win7 or yosemite vm is more painful it seems.
any instructions how to do it with heimdall, i assume i just install modem.bin or somesuch and don't have to actually flash a whole stock rom/recovery?
Click to expand...
Click to collapse
Have a look at this topic
http://forum.xda-developers.com/showthread.php?t=2545784
and especially the following post
GNUDroid said:
- Normally (if someone provided) I flash all: Modem, rpm, tz:
heimdall flash --no-reboot --MODEM NON-HLOS.bin --TZ tz.mbn --RPM rpm.mbn --verbose
- obviously just modem:
heimdall flash --no-reboot --MODEM NON-HLOS.bin
- don't forget to flash 2x!
hint to heimdall: My experience is very good. never broke anything with the mobile with this tool. Partially they changed the parameter names so on some old versions. Above command is for version 1.4.1. If you might have problems with an message "Protocol initialization", try another package from your repositories. Some compiled versions in some user repositories are not good.
Click to expand...
Click to collapse
sent from CM 12 on my S4 Mini using Tapatalk

[ROM][OFFICIAL][7.1] CyanogenMod 14.1 Nightlies for i9300

{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review.
Wiki
Official CyanogenMod Wiki: https://wiki.cyanogenmod.org/w/i9300_Info
Installation
(NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
First time CyanogenMod 14.1 installation on your Galaxy S III:
Read the official Wiki page
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the CM 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of CyanogenMod (even from 13.0) :
Update your recovery - CM Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 to automatically install updates in CM14.1)
Push the new CM 14.1 zip to your SD card
Boot into Recovery
Flash the CM 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Lastest Nightly : http://get.cm/get/i9300-latest.zip
Lastest Recovery (Nightly) : http://get.cm/get/i9300-latest-recovery.img (or TWRP)
Lastest Snapshot : http://get.cm/get/i9300-snapshot.zip
Lastest Recovery (Snapshot) : http://get.cm/get/i9300-snapshot-recovery.img (or TWRP)
Unofficial Changelog
-----------------------------------------------------------------------------
Google Apps (arm): wiki.cyanogenmod.org/w/gapps
All the builds: http://download.cyanogenmod.org/?device=i9300
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* CM version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
(see next post)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Official CyanogenMod 14.1 Nightlies, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444, Nameless, Haxynox, JustArchi
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2015-12-17
Last Updated 2016-12-25

FAQ
Robotic voice during calls?
Make sure you're on the I9300XXUGMK6 modem. Instructions are here
Root?
CM ships with root, enable developer options and look in Settings -> Developer options -> root access
Google camera crashes?
Use Google Camera from the play store, not from gapps
There's a non-device related bug? - such as SystemUI crashes triggered by performing a certain action, stray settings entries, theme crashes, translation, etc.
I just work on the device support - not something I'll fix.
Something that worked in the last nightly doesn't work in the new nightly? - bootloops? Something new is broken? It can all go here.
Quick, to the bug tracker!
Some other issue?
You can't just say 'x is broken!' and expect me to magically find the bug and fix it.
Here's what I need:
Steps to reproduce - I don't care if "it's simple". I want to know exactly what you were doing at the time of the bug. How'd it happen? Does it only happen on Tuesdays when watching a specific YouTube video? Include it *all*
What happened - in what way is this *not* the expected behaviour? Don't just say "it didn't play/upload/whatever". Did the entire phone crash? Did it show an error? Did it just show an endless progress indicator? Again, I need specifics here.
Logcat/last_kmsg - Include the whole thing please, and if your phone's been running for a while, give me a rough region of time when the issue happened. Use last_kmsg if your device reboots unexpectedly, otherwise use a logcat. (See below for info on how to get them)
How to logcat?
See here (read up to the end of the "logcat" section).
Upload it to a pastebin, include the link in your bug report.
or if you're on your phone and can't get to a computer:
Sigi_cz said:
I'd like to provide logs for problems I'm reporting, but I can't sit by my computer all the time ...
Click to expand...
Click to collapse
If you install a terminal (this one works nicely) and type this:
Code:
su
then, accept the superuser prompt, and type
Code:
logcat -d > /sdcard/logcat.txt
it should save a logcat at /sdcard/logcat.txt. You can change the filename, and it will overwrite whatever exists already at /sdcard/logcat.txt
How to get last_kmsg?
Copy /proc/last_kmsg and upload the file contents to a pastebin, include the link to that in your bug report

You're awesome! Just wanted to be the first to let you know.

Congratulations simon
From nothing be all thing :thumbup:
Inyonge Ngepos Kang GT I9300, Maen Bet Kie..

No need Flash CM12 first?

Android-Banjarmasin said:
No need Flash CM12 first?
Click to expand...
Click to collapse
no clean flash is ok

Android-Banjarmasin said:
No need Flash CM12 first?
Click to expand...
Click to collapse
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go

You are awesome

DrmohamedShawky said:
no clean flash is ok
Click to expand...
Click to collapse
haha I mean. this no need dirty flash from CM12?

Just flashed 1st nightly build.
I think there are something wrong with graphic,
Sometimes screen blinking happen here and there.
But,,,overall.
nice !!!
Finally first official nightly build released.
Thanks @forkbomb444

bandari solomon said:
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go
Click to expand...
Click to collapse
The question is this need dirty flash from CM12 or not, can it boot without flashing CM12 first?

Thank you for bringing marshmallow sweetness on out beloved s3.

Nice move
Man. You are great.

Dirty flashed via CM Updater in Settings with no Problem! Thank you so much for the hard work on our aged S3?? Keep up the great work.

Android-Banjarmasin said:
The question is this need dirty flash from CM12 or not, can it boot without flashing CM12 first?
Click to expand...
Click to collapse
No need to dirty flash... It boots up without CM12.... I'm on CM13 nightly now

bandari solomon said:
Direct clean flash is recommended... Screen flicker can be fix by turning off ambient display... All good to go
Click to expand...
Click to collapse
Thanks for info,
I will turn off ambient display, and lets see whats happen

Android-Banjarmasin said:
haha I mean. this no need dirty flash from CM12?
Click to expand...
Click to collapse
i figured out that i should say yes, no need after posting

Great ROM!
Smooth and stable.

tokict said:
Just flashed 1st nightly build.
I think there are something wrong with graphic,
Sometimes screen blinking happen here and there.
But,,,overall.
nice !!!
Finally first official nightly build released.
Thanks @forkbomb444
Click to expand...
Click to collapse
Turning off ambient display should fix it (might have to reboot).

Screen Flickering is still here after disabling ambient display

[OFFICIAL] LineageOS 14.1 - Nexus 7 2013 nightlies for 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"
}
_______________________________________________________________________________________________________________________________________________________EDIT:
This thread was originally started as CyanogenMod. This has been updated to LineageOS 14.1
New Links:
Change log. Changes
Current LineageOS Nexus7 Wi-Fi 2013 "flo" links
Device info Link
Installation instructions Link
Downloads Link
Changes Link
______________________________________________________________________________________________________________________________________________________
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review.
Wiki
Official CyanogenMod Wiki: https://wiki.cyanogenmod.org/w/Flo_Info
Installation
First time CyanogenMod 14.1 installation on your Nexus 7 (2013):
Read the official Wiki page
Unlock your bootloader if you haven't done so already
Flash a custom recovery via Fastboot
Push GApps (arm) and the CM 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 14.1 zip
Flash GApps
Reboot
Upgrading from earlier version of CyanogenMod (even from 13.0) :
Push the new CM 14.1 zip to your SD card
Boot into Recovery
Flash the CM 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Lastest Nightly : http://get.cm/get/flo-latest.zip
Lastest Recovery (Nightly) : http://get.cm/get/flo-latest-recovery.img (or use TWRP)
Lastest Snapshot : http://get.cm/get/flo-snapshot.zip
Lastest Recovery (Snapshot) : http://get.cm/get/flo-snapshot-recovery.img
-----------------------------------------------------------------------------
Google Apps (arm): OpenGApps - you'll probably only be able to use pico.
All the builds: https://get.cm/?device=flo
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Tablet information:
* CM version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Official CyanogenMod 14.1 for flo, ROM for the Nexus 7 (2013)
Contributors
forkbomb444, zwliew
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2016-11-18
Last Updated 2016-11-18

On my 32GB Flo the System partition is 840MB, clean flashing the latest CM14.1 Nightly + Nano Gapps uses about 800MB, so all we have left on the System partition is about 40MB! Now I'm wondering if we will have enough space for CM as it grows over time...
Partial log from Open Gapps Stock:
Total System Size (KB) | 847,656
Used System Space (KB) | 805,700
Current Free Space (KB) | 41,956
Additional Space Required (KB) | 426,668

18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly (I have 90 mb free on my system partition). Some users are experiencing the same issue over at the bacon forums, however my one plus one is fine on the 18.11.
The 15mb increase might be the issue?

Pezmet said:
18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly (I have 90 mb free on my system partition). Some users are experiencing the same issue over at the bacon forums, however my one plus one is fine on the 18.11.
The 15mb increase might be the issue?
Click to expand...
Click to collapse
It does seem to be somewhat buggier than the previous build, it did boot for me, and tried it without any gapps, Gello Browser would crash, tried Pico and Delta Gapps Base, both would not connect to a Google Account, Play Store would crash (those gapps worked fine on other builds). I'm back to factory stock for now. But yes, stick to Nov 17 for now.

Setting long press of the home button to launch search assistant does not work. Trying to get assistant working using the build.prop tweaks. Assistant shows in the google app, I just can't launch it. Also very flaky OK google voice detection.

What if any custom kernels are available for 14.1 and the Nexus 7 Flo? I have a pretty healthy overclock on mine, and would to keep it.

Pezmet said:
18.11 nightly does not boot for me. Twrp says that flash is successful. I am coming from 17.11 nightly
Click to expand...
Click to collapse
+1

Very nice! Using 11-17 currently.
Reposting my bugs from the old unofficial discussion thread:
osm0sis said:
Running decently!
Still the usual Nougat bug of Developer Options crash though. I also noticed the Live display interface doesn't do anything, and neither does the battery status icon choices for anything but portrait or text.
Click to expand...
Click to collapse
osm0sis said:
Maybe Developer Options only crashes when installed as MultiROM?
To avoid the log[] errors when installing, or install a Nougat ROM in MultiROM you just need a newer recovery.
Latest is here:
https://basketbuild.com/devs/Captain_Throwback/Nexus 7 2013/MultiROM
Click to expand...
Click to collapse
osm0sis said:
Noticed it didn't want to restore my Google device backup during the setup process (Google Play services kept crashing from a NPE ), so I did it manually:
Code:
bmgr list sets;
bmgr restore 1234567890abcdef
(substitute 1234567890abcdef with the code for the backup you want)
I also noticed "ringer" is showing in the volume panel, which it shouldn't, but despite editing the build.prop with the values:
ro.carrier=wifi-only
ro.telephony.default_network=9
-it still shows. Oh well. Minor bug. I'm sure they'll get to it.
Click to expand...
Click to collapse
Should be easily reproducible. I'll happily produce some logs if needed.

Nov. 19 Nightly Build:
Clean flashed with TWRP 3.0.2-0, CM and Open Gapps Nano, no problems during flashing. Booted just fine, Google Setup went normal, signed in to Google Account, Gello Browser and Play Store are not crashing. Only had a few minutes with it so far, but seems good to go!
Stay safe, use Pico!
Apps from the Play Store will be installed to the Data Partition.
Still getting CM Bug Report Stopped...

Gus Ghanem said:
Nov. 19 Nightly Build:
Clean flashed with TWRP 3.0.2-0, CM and Open Gapps Nano, no problems during flashing. Booted just fine, Google Setup went normal, signed in to Google Account, Gello Browser and Play Store are not crashing. Only had a few minutes with it so far, but seems good to go!
Stay safe, use Pico!
Apps from the Play Store will be installed to the Data Partition.
Still getting CM Bug Report Stopped...
Click to expand...
Click to collapse
Can you please confirm if night mode is available and working? It's a deal breaker for me! Thanks

utfluc said:
Can you please confirm if night mode is available and working? It's a deal breaker for me! Thanks
Click to expand...
Click to collapse
I've never used it, but if you mean under:
Settings > Display > LiveDisplay > Display mode > Night
Then no, it doesn't look like any color related settings are working. I tried all settings, a dark room, nothing, only Adaptive Brightness and Invert colors work.

I'm getting rotation stuck in portrait, a reboot didn't even resolve it. That's a deal breaker for me.
Nothing shows up in the logcat when attempting to rotate.
Edit: Disregard, happens on stock now too..

osm0sis said:
I'm getting rotation stuck in portrait, a reboot didn't even resolve it.
Click to expand...
Click to collapse
I just tried Home Screen rotation a few times, no problem. Trebuchet Allow Rotation enabled, Quick Settings on AutoRotation. Try clearing launcher data.

Does 11/19 nightly solve bootloop issue from 11/18 nightly?

MWFD said:
Does 11/19 nightly solve bootloop issue from 11/18 nightly?
Click to expand...
Click to collapse
Yes, but you should clean flash, and Nano maximum, Pico probably safer.

Gus Ghanem said:
Yes, but you should clean flash, and Nano maximum, Pico probably safer.
Click to expand...
Click to collapse
Clean flash from 11/15 nightly? Trying not to lose data everytime I flash a nightly.

MWFD said:
Clean flash from 11/15 nightly? Trying not to lose data everytime I flash a nightly.
Click to expand...
Click to collapse
If you're on Nov. 15 then try a dirty flash first.

Gus Ghanem said:
I just tried Home Screen rotation a few times, no problem. Trebuchet Allow Rotation enabled, Quick Settings on AutoRotation. Try clearing launcher data.
Click to expand...
Click to collapse
Disregard that bug report. I booted back to Marshmallow and it still doesn't work. Guess there's something up with my accelerometer. First sign my N7 has shown of aging..
Edit: and now it's working again! No rhyme or reason.

osm0sis said:
Disregard that bug report. I booted back to Marshmallow and it still doesn't work. Guess there's something up with my accelerometer. First sign my N7 has shown of aging..
Edit: and now it's working again! No rhyme or reason.
Click to expand...
Click to collapse
Mine does that to, the touchscreen stops working too. Everything comes back with a reboot
I'm going to try the hardware mod :good:
I'm using stock with a custom kernel, it's happened on everything. Bricked kernel's touchscreen fixes aren't for these issues btw, if anyone's wondering
http://forum.xda-developers.com/nexus-7-2013/general/fix-nexus-7-2013-grounding-issue-t3011140

Gus Ghanem said:
I've never used it, but if you mean under:
Settings > Display > LiveDisplay > Display mode > Night
Then no, it doesn't look like any color related settings are working. I tried all settings, a dark room, nothing, only Adaptive Brightness and Invert colors work.
Click to expand...
Click to collapse
Thanks Gus, much appreciated your report
---------- Post added at 06:40 AM ---------- Previous post was at 06:37 AM ----------
poondog said:
Mine does that to, the touchscreen stops working too. Everything comes back with a reboot
I'm going to try the hardware mod :good:
I'm using stock with a custom kernel, it's happened on everything. Bricked kernel's touchscreen fixes aren't for these issues btw, if anyone's wondering
http://forum.xda-developers.com/nexus-7-2013/general/fix-nexus-7-2013-grounding-issue-t3011140
Click to expand...
Click to collapse
My touchscreen recovered after applying that mod, there's almost no risk in trying it, I used a bit of foam tape

[OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1 for i9300

{
"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 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Wiki
Official LineageOS Wiki: http://wiki.lineageos.org/devices/i9300
Known issues
@curiousrom has a list of known issues/workarounds. You can see them here: https://forum.xda-developers.com/showpost.php?p=76224958&postcount=4419
Installation
(NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Unfortunately, now you have to wipe to come from CM - see "First time LineageOS14.1 installation on your Galaxy S III", or if you're brave try the instructions on changing keys.
First time LineageOS 14.1 installation on your Galaxy S III:
Read the official Wiki page
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the Lineage 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the Lineage 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
Push the new Lineage 14.1 zip to your SD card
Boot into Recovery
Flash the Lineage 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Install packages: https://download.lineageos.org/i9300
Google Apps (arm): https://wiki.lineageos.org/gapps
Root add-on (arm): https://download.lineageos.org/extras
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modified system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
F.A.Q.
Root?
Flashable zips to install/uninstall root can be found here. Download the "arm" variants.
Robotic voice during calls?
Try using the I9300XXUGMK6 modem. Instructions are here.
GPS Issues?
Probably a hardware issue. Try tightening the screws on the back of the device, or see this video for more information (thanks to @baltics for the link)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2017-01-25
Last Updated 2018-04-30

Reserved
Builds are up!

Reserved

Good job @forkbomb444

Extreme anxiety for the builds. Until then i will flash the new recovery

GREAT JOB!!!!!!!!!
P.S.: Why is root being shipped separately now?

I9300 Official build is now available
Lineage Os 14.1 i9300 official build is now available to download.
https://download.lineageos.org/i9300

Finally official build here.. Good job!

Do i have to flash both zips (experimental and nightlies) or i have to choose one of them? I'm in Archidroid. Sorry but i read the wiki and i'm still stuck.

bloodlithium said:
Do i have to flash both zips (experimental and nightlies) or i have to choose one of them? I'm in Archidroid. Sorry but i read the wiki and i'm still stuck.
Click to expand...
Click to collapse
Only flash experimental if coming from unofficial Lineage or CM14.
Otherwise clean install the nightly.
The ROM does not include Root.
Lineage will release it's own Root in a few days.
Chainfire's very latest revision to his 2.79 Super Su may work. I have not tried it yet on the Official Lineage ROM.
Sent from my GT-I9300 using XDA-Developers Legacy app

baltics said:
Only flash experimental if coming from unofficial Lineage or CM14.
Otherwise clean install the nightly.
The ROM does not include Root.
Lineage will release it's own Root in a few days.
Chainfire's very latest revision to his 2.79 Super Su may work. I have not tried it yet on the Official Lineage ROM.
Sent from my GT-I9300 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Successfully flash! Thanks. I think i will wait the Lineage Root. Thanks again! Greetings.

andrescm said:
GREAT JOB!!!!!!!!!
P.S.: Why is root being shipped separately now?
Click to expand...
Click to collapse
Those who want to use online secure payment Apps need unroofed devices. Whether this is the reason is just speculation.
Sent from my GT-I9300 using XDA-Developers Legacy app

Wow,it was exactly 1 moth since last official CM build.
Long live LineageOS!!!

Just to confirm..
Built-in file manager works fine and I can easily accesses external sdcard, and another thing is that last SuperSU beta (SuperSu v2.79 SR3) works for root

kiva1 said:
Just to confirm..
Built-in file manager works fine and I can easily accesses external sdcard, and another thing is that last SuperSU beta (SuperSu v2.79 SR3) works for root
Click to expand...
Click to collapse
But will we be able to switch to LOS root afterwards? Will it interfere with su?(i don't ask you directly kiva1 ,maybe someone will answer)

Great job @forkbomb444

LuciferIII said:
But will we be able to switch to LOS root afterwards?
Click to expand...
Click to collapse
Don't know for now. For this we have to wait until they release LOS root.
Sent from my Samsung GT-I9300 using XDA Labs

kiva1 said:
Don't know for now. For this we have to wait until they release LOS root.
Click to expand...
Click to collapse
I will wait till root.zip is out,then i install the latest official build. Just to be sure,i dont want to brake stuff and restore.
And how come no one talks about some of the settings reseting after Nandroid restore?

Thanks very much @forkbomb444 for sticking with us i9300'ers!

Awesome
Tonight I went from stock, to CM14 to Lineage-experimental to Lineage-nightly as smooth as butter, it's amazing. :highfive:

[ROM][Redmi 7A][PINE][10.0] LineageOS 17.1 [Unofficial]

{
"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 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
HTML:
/*
* Your warranty is now maybe void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
About project
LineageOS 17.1 (Android 10) for Redmi 7A (pine)
What's working :
•Boots
•WIFI
•Audio
•Sensors
•LED
•Hotspost
•Bluetooth
•Encryption
•Camera
•And rest things
[UPDATE-03/03/2020]
CHANGELOGS:
• Fixed in call audio
• Added support for VoLTE
Known Bugs :
•SElinux Permissive
•Expanded desktop doesn't work. LineageOS team planning to remove this feature entirely.
•APN Settings is not accessible (However, that won't cause any issues as I've included all probable APNs in my build)
Instructions
•Reboot to Recovery
•Take a full backup
•Wipe Dalvik-Cache, Cache, System, Data
•Flash the ROM
•Flash GApps (optional)
•Format Data by typing "yes"
•Flash Magisk (optional)
•Reboot to System
Downloads
ROM: lineage-17.1-20200302-UNOFFICIAL-pine.zip
GApps: Any 32 bit Gapps OpenGapps, NikGapps or BitGapps
Recovery: PitchBlack (Optional)
Magisk: Latest Magisk build (If you want root)
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
HTML:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Hit Thanks if you wanna support and like this project ;D Happy Flashing
XDA-DevDB Information
[ROM][BETA][pine][10] LineageOS 17.1, ROM for the Xiaomi Redmi 7A
Contributors
priyabratMI
YaAlex
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
ROM Firmware Required: MIUI v10.2.5.0 (MUST)
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-03-03

Good performance
Very good battery life
Ambient display not working (23.2. image)
Great work, looking forward to a final release.

This custom ROM looks like it could be worth a try. The first post says that MIUI v10.2.5.0 firmware is required but what if the Redmi 7A is on MIUI 11? Is that okay?

You have to downgrade. Otherwise lineage will not boot.

Just wanted to use this i love lineage,running on my zuk z2...but volte is what is have to use ?

partner if I want to root in the ROM just flashes magisk? or do you need to flash another plugin? Why are there some ROMs of other computers that have magisk root to flash and another complement so that something like a permission is not brickee, in this ROM for redmi 7a it is only the magisk and it starts the system?

Been using the rom a few hours. Performing amazing! The only real issue is with the in call audio as written, everything else works amazing. Maybe the signal is a bit lower than with miui, but that's fine. Hope the call audio issue gets fixed asap! Thank you! ?
Update: bluetooth audio is also not working. Completely frozen video playback when bluetooth audio device is connected.

friend did you root? and you just flashed the magisk file or some other file other than the magisk to boot the system ??

Depressing what xda have turned into.. before more people ask, yes, root is easy, just flash magisk, no need to do anything. This is not gsi or miui rom.

GabbyWC said:
This custom ROM looks like it could be worth a try. The first post says that MIUI v10.2.5.0 firmware is required but what if the Redmi 7A is on MIUI 11? Is that okay?
Click to expand...
Click to collapse
You base firmware must be MIUI v10.2.5.0 . Otherwise, it will not boot.

DebrupGhosh said:
Just wanted to use this i love lineage,running on my zuk z2...but volte is what is have to use
Click to expand...
Click to collapse
I am working on it to fix VoLTE. Please keep patience

jason2781 said:
partner if I want to root in the ROM just flashes magisk? or do you need to flash another plugin? Why are there some ROMs of other computers that have magisk root to flash and another complement so that something like a permission is not brickee, in this ROM for redmi 7a it is only the magisk and it starts the system?
Click to expand...
Click to collapse
You can just flash Magisk to root the ROM. No need of another plugins to root it..

gingerboy92 said:
Been using the rom a few hours. Performing amazing! The only real issue is with the in call audio as written, everything else works amazing. Maybe the signal is a bit lower than with miui, but that's fine. Hope the call audio issue gets fixed asap! Thank you!
Update: bluetooth audio is also not working. Completely frozen video playback when bluetooth audio device is connected.
Click to expand...
Click to collapse
Thanks for the feedback. Will fix them soon..

jason2781 said:
friend did you root? and you just flashed the magisk file or some other file other than the magisk to boot the system ??
Click to expand...
Click to collapse
It will boot without rooting. If you want to root it , you can directly flash Magisk . Not any other files required to root it other than Magisk.

Deleted

priyabrat MI said:
I am working on it to fix VoLTE. Please keep patience
Click to expand...
Click to collapse
Thank you
Are you intending to make it official once it becomes stable?

thank you for your hard work. i was about to regret paying 30usd for this phone because of the lack of software update and 3rd party development, the good battery life is the only reason i still haven't threw it out of the window ?

gingerboy92 said:
thank you for your hard work. i was about to regret paying 30usd for this phone because of the lack of software update and 3rd party development, the good battery life is the only reason i still haven't threw it out of the window ?
Click to expand...
Click to collapse
Me2 ...miui in this device is so buggy especially indian version, that i think custom rom is much better as a daily driver than this garbage
Also who wants a spyware in their mobile!?!!

After flashing the .img file I always get a black screen even after waiting for half an hour. (Same with every rom)
Help is really really really appreciated
Thank you
Redmi 7a
Arm
Android 9
Now on mokee 9 (nightly) (only this one works for me not even aosp)

DebrupGhosh said:
Thank you
Are you intending to make it official once it becomes stable?
Click to expand...
Click to collapse
Ofc

Better Mobile App

welcome